Connect your AI

Bring your own AI — Claude Desktop, or any other MCP-capable client — over a local, loopback-only connection. Your evidence never leaves your machine except to the model you personally chose.

Claude Desktop (recommended path)

Use the "Connect" button inside the Heartwood app. It writes the local MCP server registration for you — no manual JSON editing, no tokens to copy by hand.

Any other MCP client

Heartwood's local MCP server is available over both transports:

• stdio — the client launches the daemon's MCP entry point as a subprocess.
• Streamable-HTTP (loopback) — point your client at the daemon's discovered port, same discovery file and bearer token described in the API guide.

Example manual config (adapt keys to your client):

{
  "mcpServers": {
    "heartwood": {
      "url": "http://127.0.0.1:<port>/mcp",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

What your AI can do

Every tool call that creates an assertion or source requires the search/source context that produced it — the research log is a byproduct of evidence capture, never a separate "log this" step your AI can skip. See the full MCP tool reference, and the prompt cookbook for starter prompts.