Connect SuperCognit to n8n
n8n's AI Agent node can call any MCP server through the MCP Client Tool node. Point it at your SuperCognit workspace and your n8n agents can create and edit SuperCognit agents, add knowledge sources, read conversations and leads and attach tools — inside workflows that already talk to your CRM, email and databases. The REST API and webhooks cover the non-agentic direction.
Connection details
Node: MCP Client Tool
Endpoint: https://mcp.supercognit.com/platform/<workspace>/mcp
Server Transport: HTTP Streamable
Authentication: Header Auth → 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
Nightly knowledge refresh
A scheduled workflow asks the n8n agent to refresh every knowledge source that changed and posts what was re-indexed.
Leads into any system
Read new leads from SuperCognit and route them into tools SuperCognit does not integrate natively — or use webhooks for the push direction.
Agent provisioning
A form submission creates a new SuperCognit agent for a client with the right knowledge base and tools.
Conversation triage
Pull conversations that needed a human, classify them and open tickets.
How to connect
1. Copy your workspace MCP URL
Integrations → Platform MCP in the dashboard. One URL per workspace.
2. Add the MCP Client Tool node
Attach an MCP Client Tool to your AI Agent node. Endpoint: the workspace URL; Server Transport: HTTP Streamable.
3. Authenticate with a header credential
Create a Header Auth credential named x-api-key with a workspace API key from Integrations → API (Bearer auth also works).
4. Pick the tools
Choose which SuperCognit tools the agent may use — all, or a selection — and run the workflow.
Frequently asked questions
MCP when an n8n AI Agent decides what to call; the REST API (HTTP Request node) when the workflow is deterministic. Webhooks notify n8n of new conversations and leads.
Yes — expose a workflow with a Webhook node and register it as a SuperCognit tool; your customer-facing agent can then trigger it.
Works the same; the MCP endpoint is public HTTPS, so only outbound access is needed.
Use a read-only API key: the agent can list and get everything but cannot change the workspace.
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.