Connect SuperCognit to Gemini CLI
Gemini CLI loads MCP servers from settings.json and supports remote servers over streamable HTTP. Add your SuperCognit workspace and Gemini can list and edit agents, build knowledge bases, attach tools and read conversations — from the terminal, with a workspace API key or OAuth.
Connection details
// ~/.gemini/settings.json
{
"mcpServers": {
"supercognit": {
"httpUrl": "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
Scripted workspace changes
Update instructions across several agents, rotate a knowledge source or attach a new tool — described once, applied by Gemini over MCP.
Knowledge from local files
Gemini CLI reads your docs on disk and pushes them into a SuperCognit knowledge base as sources.
Daily usage check
Ask for this week's conversations, credit usage and top questions and have Gemini write the summary to a file.
Tools for Google-hosted APIs
Register your Cloud Run or Apps Script endpoints as SuperCognit tools so your customer agent can call them.
How to connect
1. Copy your workspace MCP URL
Integrations → Platform MCP in the dashboard. One URL per workspace.
2. Add the server to settings.json
In ~/.gemini/settings.json (or the project's .gemini/settings.json) add a supercognit entry under mcpServers with httpUrl set to the workspace URL.
3. Authenticate
Simplest: a workspace API key in the headers object as x-api-key. Gemini CLI can also run the OAuth sign-in for remote servers if you enable it on the entry.
4. Check with /mcp
Run /mcp inside Gemini CLI to see the server and its tools, then ask it to list your agents.
Frequently asked questions
Use httpUrl — that is Gemini CLI's key for streamable HTTP servers. url is for SSE, which SuperCognit does not serve.
Dashboard → Integrations → API. Keys are per workspace and can be read-only; keep them out of committed settings files.
It can change a product's status if the key or role allows it. Many teams keep keys read-write but leave publishing as a dashboard click.
Code Assist's agent mode in the IDE reads the same settings, so the SuperCognit server is available there too.
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.