DocumentationAPI & MCP
MCP
Plug semchat into Claude, Cursor or any MCP client, with no code.
MCP plugs semchat into an AI assistant with no code. The assistant sees semchat’s tools and uses them on its own: “what’s left in the action plan for myshop.com?”, “add these keywords”, “run a new analysis”.
Every operation of the reference is a tool with the same name, shown under each one: its path arguments and body fields are the tool’s arguments. The same key, the same workspace and the same prices as the API.
The server
| Setting | Value |
|---|---|
| Server URL | https://app.semchat.io/mcp/sse |
| Header | X-API-Key: <your key> |
Claude Code
claude mcp add --transport http semchat https://app.semchat.io/mcp/sse --header "X-API-Key: sk_live_…"Cursor
In ~/.cursor/mcp.json:
{
"mcpServers": {
"semchat": {
"url": "https://app.semchat.io/mcp/sse",
"headers": { "X-API-Key": "sk_live_…" }
}
}
}Claude Desktop
Settings → Developer → Edit config, add the server, then restart Claude. It needs Node.js.
{
"mcpServers": {
"semchat": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://app.semchat.io/mcp/sse", "--header", "X-API-Key:sk_live_…"]
}
}
}Other clients
- VS Code (GitHub Copilot), Windsurf, OpenAI’s Codex and Gemini CLI: the server URL and the header, in their own MCP settings.
- ChatGPT can’t connect yet: its connectors don’t send a key.
How the tools answer
- A tool that sends a chat message waits for the whole answer and returns it.
- An error comes back as a tool error whose message is
CODE: message, with the API’s error codes. - Up to 30 tool calls a minute per workspace.
A question this doesn’t answer? Write to us.

