Connect SuperCognit to Claude Code
Claude Code connects to remote MCP servers over streamable HTTP. Add your SuperCognit workspace with one command and your coding agent can create and edit agents, manage knowledge bases, attach tools, read conversations and run the same operations the dashboard offers — scripted, reviewable and inside the repository you already work in.
Connection details
claude mcp add --transport http supercognit \
https://mcp.supercognit.com/platform/<workspace>/mcp
# Inside Claude Code: /mcp → supercognit → Authenticate
# Or skip OAuth with a workspace API key:
claude mcp add --transport http supercognit \
https://mcp.supercognit.com/platform/<workspace>/mcp \
--header "x-api-key: <api-key>"Replace <workspace> with the workspace slug shown under Integrations → Platform MCP, and <api-key> with a workspace API key when your client does not sign in with OAuth. Published MCP servers connect the same way at their own URL.
What you can do once it's connected
Agent config as part of the repo
Keep the prompt, tools and knowledge sources of your agent next to your code. Claude Code applies changes to the workspace over MCP and you review them like any other diff.
Wire your own API as a tool
Point Claude Code at your OpenAPI spec and ask it to register the endpoints as agent tools in SuperCognit — it creates the tool definitions and attaches them to the agent.
Re-import docs on deploy
After a docs release, have Claude Code refresh the knowledge source so the support agent answers from the version you just shipped.
Debug conversations where they happen
Pull a conversation transcript, see which tool the agent called and with what arguments, fix the tool or the instructions, and test again — without leaving the terminal.
How to connect
1. Copy your workspace MCP URL
Integrations → Platform MCP in the dashboard shows the per-workspace URL and a ready-made claude mcp add command.
2. Run claude mcp add
Add the server with the http transport. Use --scope project to commit the connection to .mcp.json so your team shares it, or keep the default user scope.
3. Authenticate
Type /mcp inside Claude Code, pick supercognit and choose Authenticate — the browser opens the SuperCognit consent page. Or skip OAuth by passing a workspace API key in the x-api-key header.
4. Ask for what you need
"List my agents", "create a knowledge base from docs.example.com", "attach the booking tool to the hotel agent". Claude Code shows each tool call and asks before writes.
Frequently asked questions
Both work. OAuth is simplest on your own machine; an API key (Integrations → API) is better for CI, shared containers and read-only access, since keys can be scoped to read.
Claude Code loads newly added servers on the next start. Restart it, then run /mcp to check the connection status.
Yes — the URL is per workspace, so add each one under its own name (supercognit-acme, supercognit-demo). A key from another workspace is refused on the wrong URL.
Same operations, different surface. MCP is for an AI agent that decides which call to make; the REST API and OpenAPI spec are for code you write yourself.
Your workspace, one MCP URL away
Create a workspace, copy the MCP URL from Integrations → Platform MCP, paste it into your agent — free for 7 days.
Start buildingClaude
Add your SuperCognit workspace to Claude as a custom connector: build agents, update knowledge bases and read your inbox from a Claude chat, with one OAuth sign-in.
Claude Cowork
Give Claude Cowork access to your SuperCognit workspace: it can build agents, refresh knowledge and report on conversations as part of a longer task on your desktop.
ChatGPT
Add your SuperCognit workspace to ChatGPT as a connector: build and update agents, manage knowledge and read your inbox from ChatGPT, with OAuth sign-in and no API key.