Skip to content

Deposium MCP server

The Deposium MCP server plugs your documents, search, knowledge graph and workflows straight into your AI assistant — Claude Code, Claude Desktop, Codex, and any Model Context Protocol client.

Once connected, your assistant discovers the Deposium tools on its own — nothing to configure on that side. Just ask it to search your documents, explore the graph or run a workflow, without leaving your editor.

Before you start
Endpoint https://mcp.deposium.ai/mcp
Transport remote HTTP (Streamable HTTP), or stdio as a local bridge
Auth X-API-Key: dep_… header
Get your key app.deposium.ai → API keys

Nothing to set up tool-side

Your assistant sees the deposium_chat tool (search + sourced answer) first, plus a few macro tools. It picks the right one for your request.

Connect your client

claude mcp add --transport http deposium https://mcp.deposium.ai/mcp \
  --header "X-API-Key: dep_YOUR_KEY"

Check with claude mcp list. Ref: code.claude.com/docs/en/mcp

Claude Desktop only speaks local stdio, so bridge to the HTTP endpoint with mcp-remote. In claude_desktop_config.json:

{
  "mcpServers": {
    "deposium": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.deposium.ai/mcp",
               "--header", "X-API-Key: dep_YOUR_KEY"]
    }
  }
}

Restart Claude Desktop afterwards.

Windows / WSL

Claude Desktop runs on the Windows host, not inside WSL: Node/npx must be installed on Windows, and the file lives at %APPDATA%\Claude\claude_desktop_config.json.

In ~/.codex/config.toml — recommended: the key is read from an environment variable (DEPOSIUM_API_KEY), not written in the file:

[mcp_servers.deposium]
url = "https://mcp.deposium.ai/mcp"
env_http_headers = { "X-API-Key" = "DEPOSIUM_API_KEY" }

Quick variant (key inline in the file — less recommended):

[mcp_servers.deposium]
url = "https://mcp.deposium.ai/mcp"
http_headers = { "X-API-Key" = "dep_YOUR_KEY" }

codex mcp add supports --url/--bearer-token-env-var but no arbitrary header flag: for X-API-Key, use the TOML above. Ref: developers.openai.com/codex/mcp

Odysseus is an open-source AI workspace that acts as an MCP host. For a remote HTTP server its UI currently only supports OAuth (no custom header) — to connect with your API key, use a stdio bridge via mcp-remote.

In Settings → Integrations → MCP → Add MCP Server:

  • Transport: stdio
  • Command: npx
  • Args: ["-y", "mcp-remote", "https://mcp.deposium.ai/mcp", "--header", "X-API-Key: dep_YOUR_KEY"]

What to ask next

Once connected, try for example:

  • "Search my documents for what they say about [topic] and give me the sources."
  • "Summarise the key points of [document] with citations."
  • "Which entities are linked to [X] in my knowledge graph?"
  • "Compare what [doc A] and [doc B] say about [topic]."

Your assistant turns these into deposium_chat / deposium_query calls and answers with the source passages.

Troubleshooting

  • 401 / denied: check the X-API-Key header and that your dep_… key is active in app.deposium.ai.
  • npx not found (Claude Desktop, Windows): install Node.js on Windows, or launch via wsl.exe.
  • deposium_chat doesn't show up: restart the client after changing the config.