Use KB-1 from Claude

Claude Code can connect directly to KB-1 Local’s MCP endpoint. Use this when Claude runs on the same machine as the daemon, or when you have deliberately exposed the daemon through a private network you trust.

Prerequisites

• A running KB-1 daemon at http://127.0.0.1:7382.
• Claude Code installed locally.
• A vault id from curl http://127.0.0.1:7382/api/vaults.

Add KB-1 to Claude

claude mcp add kb1 --transport http http://127.0.0.1:7382/mcp

Then list configured servers:

claude mcp list

If your Claude CLI uses different flags, run claude mcp --help and add an HTTP or Streamable HTTP server named kb1 pointing at the same URL.

Verify from Claude

Start with a read-only prompt:

Use the kb1 MCP server. List vaults, then read README.md from demo-vault if that vault exists. Do not write anything.

Then run a reversible write:

Use the kb1 MCP server and vaultId demo-vault. Create scratch/claude-smoke.md with one sentence, read it back, then delete it permanently.

Expected signals:

• Claude calls list_vaults before using a vaultId.
• Read-only calls do not create audit rows.
• Mutating tools are audited as mcp_client.
• The scratch note appears in the local UI before it is deleted.

If Claude cannot see tools

1. Confirm the daemon is healthy:

   curl http://127.0.0.1:7382/api/health

2. Probe MCP directly:

   curl -i http://127.0.0.1:7382/mcp      -H 'content-type: application/json'      -H 'accept: application/json, text/event-stream'      --data-binary '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"claude-probe","version":"0.1.0"}}}'

3. Restart Claude after changing MCP config.

4. Make sure the URL uses the daemon port, not the internal Vite port.

Related docs

• Connect an agent through MCP
• MCP tools
• Agent access fails