Connect SuperCognit to Codex
OpenAI's Codex CLI and IDE extension connect to remote MCP servers from a single config file. Add your SuperCognit workspace and Codex can create and edit agents, build knowledge bases from your docs, register your API endpoints as tools and read conversations — as part of the coding tasks you already give it.
Connection details
# ~/.codex/config.toml
[mcp_servers.supercognit]
url = "https://mcp.supercognit.com/platform/<workspace>/mcp"
# then, in a terminal:
# codex mcp login supercognitReplace <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
Ship agent changes with the code
Change a tool's endpoint in your API and have Codex update the matching SuperCognit tool definition in the same task.
Turn an OpenAPI spec into agent tools
Codex reads your spec, creates one SuperCognit tool per operation you choose and attaches them to the agent.
Knowledge from the repository
Docs folders, changelogs, README files — Codex can push them into a knowledge base and refresh it when they change.
Investigate a bad answer
Fetch the conversation, inspect the tool calls and the cited sources, and fix the instructions or the knowledge — all in one session.
How to connect
1. Copy your workspace MCP URL
Integrations → Platform MCP in the dashboard. One URL per workspace.
2. Add the server to config.toml
Add an [mcp_servers.supercognit] table with the url to ~/.codex/config.toml, or run codex mcp add supercognit --url <url>.
3. Sign in
Run codex mcp login supercognit to complete the OAuth sign-in in your browser. If your Codex version has no OAuth login, add a workspace API key as an x-api-key header following Codex's MCP docs.
4. Work
Start Codex and ask it to list your agents. It calls the workspace tools and asks for approval before anything that writes.
Frequently asked questions
The config applies to the Codex CLI and the IDE extension on your machine. For Codex cloud tasks, use a workspace API key as the config cannot run a browser sign-in there.
Create a read-only API key under Integrations → API and share that instead of OAuth — Codex can then query but never change the workspace.
No. MCP covers the same operations. Use the REST API when you write the integration code yourself rather than letting the agent decide.
Yes, at their own URL. Published servers sign users in with an email link and meter usage 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.