Cofounder MCP server

MCP detected 2026-09-30

Details

Endpoint: https://api.superoptimizers.cofounder.co/mcp
Transport: streamable-http
Docs: https://docs.cofounder.co/cli/get-started/connect-an-agent

Authentication

OAuth 2.0 oauth2 detected 2026-09-30

OAuth · resolves from well-known metadata

OAuth 2.0 — self-onboarding

Point your MCP client at the server URL and approve access in the browser. The server supports OAuth Dynamic Client Registration (RFC 7591), so the client registers itself automatically — no developer-portal app, client_id, or client_secret to create.

Cofounder account oauth2 declared Set up OAuth ↗

OAuth · resolves from well-known metadata

Create or sign in to a Cofounder account at https://app.cofounder.co/login (email/password, Google, or GitHub). MCP clients discover the authorization server through the protected-resource metadata at https://api.superoptimizers.cofounder.co/.well-known/oauth-protected-resource and complete the hosted Supabase OAuth 2.1 flow in the browser — no manual credential is needed. The cofounder CLI runs the same flow with cofounder auth login.

Cofounder session token bearer declared

Authorization: Bearer <credential>

After cofounder auth login, run cofounder auth token (or cofounder auth token --json) to print a Supabase access token for the signed-in user. Send it as Authorization: Bearer <token> to the REST API or the MCP endpoint, or export it as COFOUNDER_API_TOKEN for the CLI. It expires with the session — mint a company API key for durable automation.