Connect SuperCognit to Cursor
Cursor's agent uses MCP servers declared in mcp.json, per project or globally. Add your SuperCognit workspace and Cursor can create and edit agents, build knowledge bases from your docs, register your endpoints as tools and inspect conversations — next to the code those tools call.
Connection details
// .cursor/mcp.json (project) or ~/.cursor/mcp.json (global)
{
"mcpServers": {
"supercognit": {
"url": "https://mcp.supercognit.com/platform/<workspace>/mcp"
}
}
}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
Tools that match your API
When you add or change an endpoint, Cursor updates the SuperCognit tool definition so the agent calls the right shape.
Project-scoped connection
Commit .cursor/mcp.json and every engineer on the project gets the same SuperCognit connection, each signing in with their own account.
Docs to knowledge base
Ask Cursor to push the docs folder into the support agent's knowledge base and re-import after each release.
Reproduce a customer conversation
Pull the transcript, see which tool call failed and fix the tool, the prompt or the endpoint in the same session.
How to connect
1. Copy your workspace MCP URL
Integrations → Platform MCP in the dashboard. One URL per workspace.
2. Add it to mcp.json
Create .cursor/mcp.json in the project (or ~/.cursor/mcp.json globally) with a supercognit entry whose url is the workspace URL. Cursor Settings → MCP shows the same list.
3. Sign in or add a key
Cursor marks the server as needing login — click it to run the OAuth sign-in. For a key instead, add a headers object with x-api-key.
4. Use it from the agent
The SuperCognit tools appear in the agent's tool list. Cursor shows each call and asks before writes unless you allow them.
Frequently asked questions
Project when the agent belongs to that codebase; global when you manage several workspaces from one machine. Both can coexist under different names.
Check the URL ends with /mcp, that the workspace slug is right, and that you completed the sign-in. Restart the MCP server from Cursor's settings after editing the file.
It works, but OAuth is better: each person signs in with their own SuperCognit account and the audit trail stays per user.
The platform MCP is rate-limited per key or session (generous for interactive use). Conversations your agents have with customers are metered as usual.
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 Code
Add your SuperCognit workspace to Claude Code with one command. Create agents, update knowledge bases and wire tools from the terminal, with OAuth or a workspace API key.
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.