MCP server

Overview

The Model Context Protocol (MCP) is an open standard that lets an AI client call tools on a server. LiveContext exposes its agent tools through one MCP endpoint, using the Streamable HTTP transport and JSON-RPC 2.0. Any client that supports remote HTTP servers can connect with an API key.

The MCP server is available on LiveContext Cloud and on the self-hosted Community Edition. Everything you do through it runs as you, on your own account and data.

Find your connection details

Go to Settings > MCP Server. The page has three sections:

Create an API key

Every request to the endpoint needs an API key: lc_live_ followed by 64 hexadecimal characters. Create one key per client so you can revoke one without breaking the others. A key expires 365 days after you create it: the list shows its expiry date, and an expired key no longer connects, so create a new one before then.

The plan that counts is the one of the workspace the key acts in: the higher of your own plan and the plan of the workspace's owner. A member of a Team workspace can therefore create keys for that workspace even on a Free plan of their own. If your plan later includes fewer keys than you hold, your oldest keys keep working and the newer ones stop until you revoke one or upgrade.

1. 1
   Start a new key

   In Settings > MCP Server, under API keys, select New key.
2. 2
   Name it

   Type a Name that says which client uses it, for example "Cursor on my laptop".
3. 3
   Pick the workspace

   Under Workspace, choose where the key acts. It starts on the workspace open in the app. A client using the key works only in that workspace and cannot switch to another one; create one key per workspace if a client needs several.
4. 4
   Choose the access

   Leave Limit to specific tools off to give the key access to all MCP tools. Turn it on to choose tools one by one under Tools; you must pick at least one.
5. 5
   Copy the key

   Select New key. The Key created dialog shows the full key once. Copy it now, then select Done. The list only shows a masked hint afterwards.

To revoke a key, select the Revoke (bin) icon next to it, then Revoke key. Revocation is immediate, and every client configured with that key stops connecting.

Full access or limited to specific tools

Authentication

Send the key in either header. Use the first form unless your client only supports Authorization:

X-API-Key: lc_live_xxxxxxxx
Authorization: Bearer lc_live_xxxxxxxx

A request without a valid key gets 401 Unauthorized with a WWW-Authenticate: Bearer challenge, so your client reports a credentials problem.

Connect a client

The Client configuration section of the settings page offers the three snippets below, with your endpoint URL already filled in. Replace YOUR_API_KEY with the key you created. The examples use the cloud URL; on a self-hosted instance, copy the snippets from your own settings page.

Claude Code

Run this command once in a terminal. It adds the server to Claude Code under the name livecontext.

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Cursor, Claude Desktop, and other JSON configurations

Clients that read an mcpServers configuration file take this JSON block. Add the livecontext entry to the file your client uses; its location depends on the client, so check the client's own documentation, and make sure your version supports remote HTTP servers.

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Codex

Add these lines to ~/.codex/config.toml:

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Other clients

Any client that speaks MCP over Streamable HTTP works: point it at the endpoint URL and send the key in the X-API-Key header (or Authorization: Bearer).

Which tools are exposed

The server exposes the same tools as the LiveContext agent in chat, for example workflow (build, run, and inspect workflows), table (your tables), catalog (search and call your connected integrations), interface, and files. The exact list for your install is the one under Tools when you create a limited key, and the one your client receives from tools/list. The Endpoint section shows how many there are.

Integrations are not listed one tool per endpoint: your client reaches them through the catalog tool, with the connections you set up in LiveContext. See Integrations.

Protocol details

Cloud and Community Edition

The endpoint, the keys, the workspace a key acts in, the headers, and the 403 scope_forbidden rule behave the same in both editions. A self-hosted install has no plan limit on keys. The endpoint URL differs: on a self-hosted instance it is built from the public address configured for your install, and the Endpoint section of your own settings page shows it. The per-minute request ceilings described in REST API & webhooks are those of LiveContext Cloud.

Troubleshooting

Related pages