@live-context/mcp

Stdio MCP proxy for Live Context — your team's shared AI knowledge layer. This package is a thin client that forwards MCP tool calls to the hosted API at live-context.com/api/mcp/*. It does not connect to any database directly. The only thing your machine needs is an MCP API key.

Install

The fastest path is the dashboard's one-liner. After signing in at live-context.com, go to Settings → MCP, copy your key, and run:

claude mcp add live-context -e MCP_API_KEY=<your-key> -- npx -y @live-context/mcp

Restart Claude Code. Live Context is now wired in.

Manual configuration

For Claude Desktop, Cursor, or any other MCP client, add this to your mcpServers config:

{
  "mcpServers": {
    "live-context": {
      "command": "npx",
      "args": ["-y", "@live-context/mcp"],
      "env": {
        "MCP_API_KEY": "<your-key>"
      }
    }
  }
}

Remote (HTTP) transport

Live Context also exposes a Streamable HTTP MCP transport at https://live-context.com/api/mcp/mcp. Use this when you'd rather not install Node — Claude Code, Cursor, Codex CLI, and ChatGPT Developer Mode all support paste-in URLs with custom headers.

Claude Code remote:

claude mcp add --transport http live-context https://live-context.com/api/mcp/mcp \
  --header "Authorization: Bearer <your-team-key>" \
  --header "X-LC-User-Token: <your-user-token>"

Cursor / Claude Desktop / any "URL + headers" client:

{
  "mcpServers": {
    "live-context": {
      "url": "https://live-context.com/api/mcp/mcp",
      "headers": {
        "Authorization": "Bearer <your-team-key>",
        "X-LC-User-Token": "<your-user-token>"
      }
    }
  }
}

The HTTP endpoint is authenticated with the same team key + (optional) user token as the stdio proxy. Both transports talk to the same backend and expose the same tools.

A dashboard-driven one-click install flow (OAuth-based — no token pasting) is on the way; until then, the snippets above are the canonical Remote setup.

Environment variables

| Variable | Required | Purpose | | --- | --- | --- | | MCP_API_KEY | yes | Your team's lc_team_… key from Settings → MCP. | | LC_USER_TOKEN | no | Personal token for notebook-scoped reads/writes. | | LC_API_BASE_URL | no | Override the API base. Defaults to https://live-context.com. |

Tools

Read — get_context, list_spaces, list_collections, list_notebooks, list_context

Write — write_context (knowledge → Spaces or Notebooks). Honors write_mode='review_required' Spaces: writes to those queue as proposals for admin approval. Pass trigger_message (min 10 chars) explaining why the write should be applied when targeting such a Space.

Propose (v0.4.0+) — propose_space, propose_project, list_my_proposals. Use these when the user asks for a new container. Both propose_* tools require a trigger_message (min 10 chars). Auto-approves when the caller is a team admin; otherwise queues for review at live-context.com/dashboard/proposals.

Health — health_check

See the Live Context docs for full schemas and examples.

Get a key

live-context.com/dashboard/settings/mcp