Connecting

MCP configuration

HUSK exposes a standard MCP endpoint at /mcp. Any MCP-compatible client can connect using HTTP transport with a Bearer token.

Per-project

Create .mcp.json in your project root:

{
  "mcpServers": {
    "husk": {
      "type": "http",
      "url": "http://localhost:3000/mcp",
      "headers": {
        "Authorization": "Bearer husk_your-api-key-here"
      }
    }
  }
}

Global (all projects)

Place the same file at ~/.claude/.mcp.json so every Claude Code session has access.

Claude Code plugin

The plugin adds session-end hooks and skills on top of the MCP tools:

claude plugin add /path/to/HUSK/plugins/claude-code

Environment variables

The plugin needs to know where HUSK is running:

Set them in your shell profile or .env file.

Verifying the connection

After connecting, ask Claude Code to run a quick test:

Search my HUSK memories for "test"

If everything is wired up, you'll see results (or an empty list if this is a fresh install). If you see an error about the MCP server being unavailable, check that HUSK is running and the API key is correct.