Connect SuperCognit to Cline
Cline connects to remote MCP servers over streamable HTTP from its MCP settings. Add your SuperCognit workspace and Cline can create and edit agents, push docs into knowledge bases, register tools and read conversations — with the per-step approvals Cline already gives you.
Connection details
// cline_mcp_settings.json
{
"mcpServers": {
"supercognit": {
"type": "streamableHttp",
"url": "https://mcp.supercognit.com/platform/<workspace>/mcp",
"headers": { "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 changes as reviewed steps
Cline shows each MCP call before it runs, so updating instructions or attaching tools is as reviewable as a file edit.
Knowledge from the repo
Push docs, READMEs and changelogs into a knowledge base and refresh them when they change.
Tools from your endpoints
Register API operations as SuperCognit tools and attach them to the agent that needs them.
Conversation forensics
Fetch a transcript with its tool calls, find the failing step and fix it in the same task.
How to connect
1. Copy your workspace MCP URL
Integrations → Platform MCP in the dashboard. One URL per workspace.
2. Add a remote server
Open Cline's MCP Servers panel → Remote Servers, enter supercognit and the URL — or edit cline_mcp_settings.json with a streamableHttp entry.
3. Add a workspace API key
Add a headers object with x-api-key (keys live under Integrations → API). Read-only keys are fine for querying.
4. Use the tools
Cline lists the SuperCognit tools under the server and asks for approval per call unless you auto-approve specific ones.
Frequently asked questions
streamableHttp. SuperCognit does not serve SSE or stdio; it is a remote HTTP server.
Yes — Cline lets you auto-approve per tool. Approving the list and get tools while keeping writes manual is a sensible default.
The same MCP settings apply wherever Cline runs; a workspace API key avoids needing a browser.
Connect it at its own URL. Customers sign in by email link and usage is metered per user.
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.