Connect an Agent

Cofounder runs a hosted MCP server, and your agent talks to it directly:

https://api.superoptimizers.cofounder.co/mcp

Point a compatible client at that URL and it gets the full tool surface — roughly 280 tools covering companies, knowledge, providers, deploys, communication, and operations. No CLI install, no local process to babysit. These are the same operations the CLI and API expose.

The fast way: cofounder mcp setup

If you have the CLI installed, it writes the config for you:

cofounder mcp setup

It configures Claude Code and Codex by default and leaves your other MCP servers alone. Pass --client claude, --client codex, or --client cursor to pick one, and --print to see what it would write without touching anything.

• Claude Code — .mcp.json in the current directory
• Codex — ~/.codex/config.toml
• Cursor — ~/.cursor/mcp.json

Adding it by hand

Every client stores its MCP servers in a JSON or TOML file, so you can add a cofounder entry yourself.

Claude Code — .mcp.json in your project:

{
  "mcpServers": {
    "cofounder": {
      "type": "http",
      "url": "https://api.superoptimizers.cofounder.co/mcp",
      "headers": { "Authorization": "Bearer ${COFOUNDER_API_TOKEN}" }
    }
  }
}

Codex — ~/.codex/config.toml:

[mcp_servers.cofounder]
url = "https://api.superoptimizers.cofounder.co/mcp"
bearer_token_env_var = "COFOUNDER_API_TOKEN"

Cursor — ~/.cursor/mcp.json. Cursor interpolates env vars differently from Claude Code:

{
  "mcpServers": {
    "cofounder": {
      "url": "https://api.superoptimizers.cofounder.co/mcp",
      "headers": { "Authorization": "Bearer ${env:COFOUNDER_API_TOKEN}" }
    }
  }
}

For any other client, it's the same recipe: the streamable-HTTP URL plus a bearer token.

Signing in

You have two options:

• OAuth sign-in. If your client supports MCP OAuth, the first connect opens a browser sign-in and you're done — nothing to store.
• Bearer token. Export COFOUNDER_API_TOKEN in the agent's environment. cofounder auth token prints one from a signed-in CLI; for anything durable, mint a company API key with cofounder company api-keys create — see API Keys and Scripting.

Clients that can't reach HTTP

Some clients only speak stdio, so the CLI ships a bridge:

cofounder mcp stdio --configure claude

--configure prints the config block to paste into your client, which then runs cofounder mcp stdio as the server process. The bridge calls the same hosted endpoint, so the same auth applies.

More than tools

Tools are most of the surface, not all of it. The server also exposes your company's skills (skill://) and Library files as resources, prompts that show up as slash commands, and a CRM board for clients that render MCP apps — covered in MCP Beyond Tools.

A few capabilities aren't on MCP today — credential minting and managed Stripe object operations. Pages mark them where they come up; the CLI covers them.

Next steps