All pages

Connect your assistant

Add the Katexs MCP server to Claude Code, Cursor, VS Code or Claude Desktop with an API key.

You need a server key — create one in Settings → API keys. The same page shows these snippets ready to copy, under Connect an AI assistant.

Pick what the assistant may do

The key's access decides which tools your assistant even sees:

KeyThe assistant can
Build (recommended)Build agents, connect your API, manage contacts and webhooks, read everything, test-chat the agent — but not message anyone or place calls
Read-onlyRead conversations, calls, contacts and settings — for reports and dashboards
Full accessEverything above, plus sending, calling and code sends — each still asking for your approval

Start with Build. Create a separate full-access key only when you want the assistant to send or call, and revoke it when you are done.

Warning

The key can message your customers and place calls. Keep it in your assistant's config on your own machine — never in a repository, a shared document or a web page. If it leaks, revoke it in Settings → API keys; that takes effect immediately.

Claude Code

Run in a terminal:

claude mcp add --transport http katexs https://app.katexs.com/api/v1/mcp \
  --header "Authorization: Bearer ta_live_YOUR_KEY"

Check it with claude mcp list, or /mcp inside a session.

Cursor

Add to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "katexs": {
      "url": "https://app.katexs.com/api/v1/mcp",
      "headers": { "Authorization": "Bearer ta_live_YOUR_KEY" }
    }
  }
}

VS Code

Add to .vscode/mcp.json:

{
  "servers": {
    "katexs": {
      "type": "http",
      "url": "https://app.katexs.com/api/v1/mcp",
      "headers": { "Authorization": "Bearer ta_live_YOUR_KEY" }
    }
  }
}

Claude Desktop and others

Clients that only run local servers connect through mcp-remote, which needs Node.js. In Claude Desktop: Settings → Developer → Edit config:

{
  "mcpServers": {
    "katexs": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://app.katexs.com/api/v1/mcp",
               "--header", "Authorization:${AUTH}"],
      "env": { "AUTH": "Bearer ta_live_YOUR_KEY" }
    }
  }
}

The key is passed through env deliberately: some clients split arguments on spaces, which breaks Bearer ta_live_… written inline.

Check it works

Ask your assistant: "List my Katexs agents." It should call list_agents and show them.

If it does not connect

You seeWhyFix
401 UnauthorizedThe key is missing, mistyped or revokedCopy the full key, including ta_live_; create a new one if it was revoked
405Something opened the address with GETUse the http / Streamable HTTP transport — the server is POST-only and keeps no session
A tool answers 429Over 240 requests a minute for the workspace, or a send/call limitWait the number of seconds it gives and retry
Tools refuse with "Not run"Working as designed — the action needs your approvalApprove it, and the assistant runs it again. See Safety