@asphodel/soul-mcp

Connect any AI tool to your Asphodel memory graph via the Model Context Protocol.

One API key. Persistent memory across Claude Code, Cursor, Windsurf, or any MCP-compatible tool.

Setup

1. Get an API key at asphodel.ai (free tier available)

2. Add to your MCP config:

Claude Code (~/.claude/settings.json)

{
  "mcpServers": {
    "soul": {
      "command": "npx",
      "args": ["-y", "@asphodel/soul-mcp"],
      "env": {
        "SOUL_API_KEY": "sk_soul_your_key_here"
      }
    }
  }
}

Cursor / Windsurf (.cursor/mcp.json or .windsurf/mcp.json)

{
  "mcpServers": {
    "soul": {
      "command": "npx",
      "args": ["-y", "@asphodel/soul-mcp"],
      "env": {
        "SOUL_API_KEY": "sk_soul_your_key_here"
      }
    }
  }
}

Tools

| Tool | Description | |---|---| | soul_session_init | Initialize/resume a session — loads context from your memory graph | | soul_memory_write | Persist a memory (decisions, facts, code patterns) | | soul_session_load | Refresh session context mid-conversation | | soul_topics_lookup | Retrieve memories by topic keywords | | soul_topics_top | See your most active topics across all sessions |

Environment Variables

| Variable | Required | Default | Description | |---|---|---|---| | SOUL_API_KEY | Yes | — | Your sk_soul_ API key from asphodel.ai | | SOUL_SESSION_ID | No | "default" | Default session ID if not specified per-call | | SOUL_API_URL | No | Production URL | Override for self-hosted deployments |

Usage in Claude Code

Once connected, Claude can automatically persist memory:

You: Remind me we're using Stripe for billing and Supabase for auth.
Claude: [calls soul_memory_write with topics: ["billing", "stripe", "auth", "supabase"]]
        Saved to your memory graph.

--- next session ---

You: What stack are we using?
Claude: [calls soul_session_init → loads previous context]
        You're using Stripe for billing and Supabase for auth.

License

Apache-2.0 — free to use, modify, and self-host.