Claude and Codex

Sokko has an MCP server for your own AI client. Connect it once, and the model in Claude Code, Codex CLI, Cursor, claude.ai, Claude Desktop or ChatGPT can list and create your agents, hand a task to an agent and read its answer, import your memory and skills into Sokko, and recall what Sokko Memory knows.

The connection acts as you, in one workspace, with your role. There are two ways to connect:

• An API key, for Claude Code, Codex CLI and Cursor. The key goes in the client's configuration.
• Sign in with Sokko, for claude.ai, Claude Desktop, ChatGPT and codex mcp login. You approve the app in your browser and pick the workspace. No key to copy.

Connect with an API key

claude mcp add --transport http sokko https://sokko.ai/api/mcp/workspace --header "Authorization: Bearer sk_live_..."

export SOKKO_API_KEY=sk_live_...
codex mcp add sokko --url https://sokko.ai/api/mcp/workspace --bearer-token-env-var SOKKO_API_KEY

{
  "mcpServers": {
    "sokko": {
      "url": "https://sokko.ai/api/mcp/workspace",
      "headers": { "Authorization": "Bearer sk_live_..." }
    }
  }
}

For a team, put the server in the project's .mcp.json and share the key as the SOKKO_API_KEY environment variable:

{
  "mcpServers": {
    "sokko": {
      "type": "http",
      "url": "https://sokko.ai/api/mcp/workspace",
      "headers": { "Authorization": "Bearer ${SOKKO_API_KEY}" }
    }
  }
}

Connect with Sign in with Sokko

In claude.ai, Claude Desktop or ChatGPT, add a custom connector (claude.ai: Settings → Connectors → Add custom connector; ChatGPT: Settings → Connectors → Create) with this URL:

https://sokko.ai/mcp

The app opens a Sokko page in your browser. Sign in, choose the workspace the app may use, and approve. The app is connected for 90 days; after that Sokko asks you to approve again.

For Codex CLI without a key:

codex mcp add sokko --url https://sokko.ai/mcp
codex mcp login sokko

The browser opens the same approval page.

An app connected this way shows in Settings → Connected apps. Revoke it there to end its access at once. An owner or admin sees and revokes every member's connections; other members see their own.

What the tools do

A conversation started from your client shows in the agent's chat in the dashboard, under your name.

Memory tools need the Sokko Memory add-on. Without it they answer with a 402 error and the client tells you to enable the add-on.

Hand a task to an agent

Your client has the handoff prompt. In Claude Code, type /sokko:handoff and give the task. The model lists your agents, picks one or asks you, sends the task with sokko_agent_ask, waits with sokko_agent_wait, and reports the answer.

A tool call waits at most 50 seconds. A long task returns status: running with a turnId. The model calls sokko_agent_wait again until the agent is done. The agent keeps working between calls.

Import your memory

Your client has the import_memory prompt. In Claude Code, type /sokko:import_memory. The model reads its own memory files, shows you the list, and imports them after you confirm:

• Claude Code: MEMORY.md and the memory/*.md files of the project, plus CLAUDE.md.
• Codex: AGENTS.md, plus ~/.codex/memories/*.md when that folder exists.

Sokko keeps the file names in its memory namespace: MEMORY.md stays MEMORY.md, CLAUDE.md becomes memory/claude-md.md, and every other file becomes memory/<file name>. A file whose content did not change since the last import is skipped, so you can run the prompt as often as you like.

Build a custom agent

The builder tools let your client drive the Sokko builder the way the sokko CLI does. Each step maps to one thing you would do in the dashboard:

1. Create a project. Say "create a custom agent called Support bot". The model calls sokko_builder_create.
2. Describe a change. Say what the agent must do, in one instruction. The model calls sokko_builder_change with your words and what a correct result looks like, then sokko_builder_wait until the builder has a new revision. One instruction opens one change request. If the builder asks a question, the model shows it to you and sends your reply as the next instruction.
3. Test it. The model calls sokko_builder_test, which starts the preview and sends the agent a message. It shows you the agent's answer. If the agent asks something, the model shows the question and sends your answer. sokko_builder_diff shows the files the builder changed.
4. Say whether it is right. Your words go into sokko_builder_assess as the verdict. The model must not judge the answer for you.
5. Deploy. When you say "deploy it", the model calls sokko_builder_publish with your words and waits with sokko_builder_wait until the agent is live. A publish deploys every unpublished change of the project, not only the last one.

Sokko refuses a publish without a test of that revision that you assessed as passed. The project's saved settings deploy: the connection grants, memory, CPU and memory limits are not changed from your client. Open the project in the dashboard (the builderUrl in every answer) to change them.

The builder tools appear only when the builder is enabled for your Sokko deployment, and they need Sokko Credits.

Limits

• One connection is bound to one workspace. Connect a second workspace with a second key and a second server name, or approve the app again and pick the other workspace.
• A client may send 120 requests per minute. Creating an agent, asking an agent, importing memory or skills, and the builder's create, change, test and publish are limited to 20 per minute.
• A Sign in with Sokko connection lasts 90 days. The app then asks you to approve again.

Revoke the key in Settings → API keys, or the app in Settings → Connected apps, to end the connection.