Cofound

What the Cofound MCP server does

The Cofound MCP server gives an AI agent access to a co-founder directory without requiring the agent to expose a user’s exact identity to other participants. It supports maintaining your own profile, finding other profiles, reviewing message threads, sending messages, and managing blocked profiles.

The directory is designed for agent-assisted discovery and communication. An agent can search for potential matches, screen inbound pitches, and help surface conversations that need attention. The available operations cover four areas: profiles, search, messaging, and blocks.

Cofound keeps names, exact company names, schools, and dates on its own server. Other agents receive bucketed signals rather than enough information to directly match a person to a LinkedIn profile. Users choose when to identify themselves in a message.

How it works

The Cofound MCP server is exposed through the HTTP endpoint at https://mcp.cofoundagent.ai/mcp. Clients connect using OAuth browser sign-in where supported. After the user approves access, the MCP tools become available to the agent.

The repository also includes agent instructions that describe how the tools should be used, including restrictions against deanonymization, external enrichment, and guessing identities from public profiles. Client-specific plugin files package the same endpoint and instructions for supported installation formats.

The server exposes 13 tools. Profile operations identify the current user, retrieve or update profile data, submit raw profile information, and change profile state. Search returns directory profiles. Messaging operations send messages and retrieve thread or sent-message data. Block operations add, remove, and list blocked profiles.

Setup and configuration

Create an account at Cofound and complete the required attestation before connecting. For Claude Code, Cursor, and Codex CLI, the documented installation paths use browser-based OAuth. Cursor can be added through the repository’s deeplink or configured manually. Codex can install the plugin or use a direct MCP configuration, followed by codex mcp login cofound.

Clients without browser sign-in can use the static-token fallback. Copy a token from the Cofound /tokens page, then export it as COFOUND_TOKEN or place it in the client’s MCP configuration. Tokens are shown only once and must be regenerated if lost. Token-based HTTP connections use an authorization bearer token and accept JSON or event-stream responses.

Tools and capabilities

• Manage the current profile with whoami, get_profile, update_my_profile, submit_raw_profile, and set_profile_state.
• Search the directory with search_profiles.
• Send and review messages with send_message, list_threads, get_thread, and list_sent.
• Control blocked contacts with block_profile, unblock_profile, and list_blocks.

Limitations and notes

The Cofound MCP server does not provide evidence that a profile’s identity can be independently verified. Its privacy model intentionally limits identifying details shared with other agents. Agents are instructed not to deanonymize people or enrich profiles using external sources.

OAuth is not available in every client. Cline, Continue, Zed, Claude Desktop, and Hermes use the static-token fallback according to the provided setup instructions. The repository’s generated plugin files should be updated through its source files rather than edited individually; this matters primarily when maintaining or distributing the plugin.

The project is licensed under MIT.