Getting Started

Connect your AI assistant to Multiplist in under 5 minutes. Install @multiplist/mcp-server via npm or connect directly over StreamableHTTP — then make your first vault search.

# Connect via MCP

Multiplist works as an MCP server. Connect from Claude Desktop, Claude Code, ChatGPT, or any MCP-compatible client.

• Endpoint: https://multiplist.ai/mcp
• Transport: StreamableHTTP + OAuth 2.1 with PKCE
• npm: @multiplist/mcp-server@1.0.0

# Claude Desktop — Option A: Remote (recommended)

Add this to your claude_desktop_config.json:

{
  "mcpServers": {
    "multiplist": {
      "type": "streamable-http",
      "url": "https://multiplist.ai/mcp"
    }
  }
}

Transport: StreamableHTTP + OAuth 2.1 with PKCE. On first use, Claude opens the Multiplist login page in your browser — the token is stored automatically. No API keys to manage.

# Claude Desktop — Option B: Local bridge via npm

Install the bridge globally:

npm install -g @multiplist/mcp-server

Then add this to claude_desktop_config.json:

{
  "mcpServers": {
    "multiplist": {
      "command": "npx",
      "args": ["-y", "@multiplist/mcp-server"],
      "env": {
        "MULTIPLIST_MCP_TOKEN": "mcp_live_..."
      }
    }
  }
}

Generate your MCP Token in Settings → MCP Tokens inside the Multiplist app (prefix mcp_live_). The bridge forwards every call to https://multiplist.ai/mcp — no local database required.

Note: This bridge requires an MCP Token, not a REST API Key. The two are different systems with different prefixes. The legacy env var MULTIPLIST_API_KEY still works (the value has always been an MCP Token despite the name), but MULTIPLIST_MCP_TOKEN is preferred for new configs.

# Claude Code

One command:

claude mcp add multiplist --transport streamable-http https://multiplist.ai/mcp

Claude Code handles OAuth automatically. When the server requires authentication, your browser opens the login page and the token is stored for future sessions.

# ChatGPT

ChatGPT connects through the Apps & Connectors interface.

1. Open ChatGPT → Settings → Apps & Connectors.
2. Click Add and enter the URL https://multiplist.ai/mcp/chatgpt.
3. Set the auth method to OAuth and click Create.
4. Log in with your Multiplist account.

# Your first search

Once connected, try these prompts to verify everything works:

• "Search my Multiplist vault for recent notes" → triggers search_vault.
• "Give me an overview of my vault" → triggers get_vault_summary.
• "Import this text into my vault: [paste content here]" → triggers create_source.

# Your first useful loop

Once you're connected, the loop that gets agents fluent fastest:

Source → Seeds → Search → Brief → Annotate.

1. Create a Source. "Save this conversation to my vault." → create_source
2. Watch Seeds extract. Decisions, frameworks, golden passages, and the rest land automatically with provenance to exact character ranges.
3. Search the vault. "What have I decided about pricing?" → search_vault
4. Request a Brief when a question spans many sources. "How has my thinking on onboarding evolved?" → request_brief
5. Annotate when a source needs a correction or evolution note. → add_marginalia

You don't need to understand every primitive before starting. Push something in. See what comes back. The vocabulary follows the work.

# Key concepts

• Sources — the atomic unit of imported content. Conversations, documents, transcripts, notes.
• Seeds — structured insights extracted from sources. Eight categories: decisions, frameworks, golden passages, definitions, actions, questions, offers, emergence.
• Containers — top-level domains for organizing studios.
• Studios — focused workspaces where active work happens on a specific topic.
• Extraction — the semantic engine that reads sources and produces categorized, cited seeds.
• Skills — custom extraction recipes you define. Tell Multiplist what to look for in your specific content type.

# Authentication

Multiplist supports two authentication methods:

MCP tokens use the mcp_live_ prefix (legacy tokens issued before May 2026 are 64-char hex with no prefix and remain valid), are SHA-256 hashed at rest, and support scoped permissions. Tokens are shown only once at creation — store them securely.

If you're using the REST API (/api/v1/*) instead of MCP, you need a separate API Key with the mp_live_ prefix from Settings → API Keys. The two systems aren't interchangeable — see Authentication for the full breakdown.

# Next steps

• MCP Tool Flow Map — every tool mapped by intent.
• MCP Tools Reference — parameter-level detail for every tool.