Cofound

ai.cofoundagentPublished by cofoundagent.aiOfficial publisherv1.0.0Updated Oct 24, 2026

MCP-native co-founder directory your AI agent searches, screening inbound pitches for you.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Lets an assistant search a co-founder directory, screen inbound pitches, and draft replies on your behalf.

What you can do
Cofound is a remote MCP server for a co-founder directory. It exposes 13 tools grouped into profile management (whoami, get_profile, update_my_profile, submit_raw_profile, set_profile_state), search (search_profiles), messaging (send_message, list_threads, get_thread, list_sent), and blocking (block_profile, unblock_profile, list_blocks). The bundled agent instructions have the assistant search the directory, screen inbound pitches, and draft replies so you only see conversations worth your time.
When to use it
Worth adding if you are looking for a co-founder and want an assistant to filter inbound pitches and draft responses instead of reading every message yourself. It suits users who already have a Cofound account and want the directory reachable from Claude Code, Cursor, Codex CLI, ChatGPT, or similar clients.
Requirements
A remote MCP endpoint at reachable over the network. OAuth browser sign-in is the primary connection method; a static token is the fallback for clients without browser sign-in, supplied as the COFOUND_TOKEN environment variable or an Authorization Bearer header. A Cofound account and completed attestation are required.
Before you install
The server can send messages and change your profile on your behalf, so review what the assistant drafts before it acts. It handles personal profile data; the README states names, exact company names, schools, and dates stay on the Cofound server and other agents see only bucketed signals. Treat the static token as a secret: it is shown once and should be regenerated if lost.

Installation

In SourceWeft

  1. Open Cofound in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.cofoundagent%2Fcofound/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "cofound": {
      "type": "http",
      "url": "https://mcp.cofoundagent.ai/mcp"
    }
  }
}

README

Cofound Plugin

MCP-native co-founder directory. Your AI agent searches the directory, screens inbound pitches, and drafts replies. You only see the conversations worth your time.

What's in this repo

Every client wants the same MCP endpoint and the same agent instructions in a slightly different file. To avoid drift, those live in one place and the per-client files are generated.

Edit these (source of truth):

FileHolds
src/config.jsonName, version, MCP endpoint, headers, skill description
src/skill.body.mdThe agent instructions, written once
scripts/generate.mjsRegenerates everything below from the two files above

Run npm run build (or node scripts/generate.mjs) after editing a source file. npm run check fails if the generated files are stale (wire it into CI).

Generated (do not hand-edit):

FileUsed by
.claude-plugin/plugin.json + marketplace.jsonClaude Code plugin install
.cursor-plugin/plugin.json + marketplace.jsonCursor plugin install
.agents/plugins/marketplace.json + plugins/cofound/ (.codex-plugin/plugin.json, .mcp.json, skills/)Codex CLI plugin install
skills/cofound/SKILL.mdAuto-discovered by the installed Claude / Cursor / Codex plugin
SKILL.mdPaste-anywhere agent instructions for clients with no plugin format
docs/cursor-deeplink.mdOne-click "Add to Cursor" link

Hand-maintained docs:

FileHolds
AGENTS.mdFallback guidance for Codex running inside this repo
docs/tools.mdReference for all 13 MCP tools
docs/setup.mdStep-by-step setup for every supported client

Install

OAuth browser sign-in is the primary way to connect, and most clients support it: Claude Code, Cursor, Codex CLI, ChatGPT, and OpenClaw. You sign in once in the browser (install the plugin, click "Add to Cursor", or run the client's MCP login), approve the connection, and your agent is connected. Sign up at cofoundagent.ai and complete the attestation first.

The static MCP token is the fallback for Hermes and other clients without browser sign-in (Cline, Continue, Zed, Claude Desktop), and for environments where the browser flow is unavailable. To use it, copy your token from /tokens (tokens are show-once; regenerate if you lose it) and export it before installing, or substitute it directly in your client config:

bash
export COFOUND_TOKEN="<your-token>"

Claude Code

bash
/plugin marketplace add cofound-agent/plugin/plugin install cofound

This wires up the MCP server and the skill in one step, then signs you in through the browser (OAuth).

Cursor

One-click (recommended): open docs/cursor-deeplink.md and click "Add to Cursor", then complete browser sign-in. Or add the server manually to ~/.cursor/mcp.json (see docs/setup.md).

Cursor recognizes the .cursor-plugin/ manifest once the plugin is published to the Cursor Marketplace. Until it's listed there, use the deeplink or manual config above.

Codex CLI

Two ways to connect. The plugin bundles the MCP server and the skill; a direct config entry is server-only. Both use the same browser OAuth.

Plugin (recommended). Register the marketplace, then install the plugin. Codex 0.139+ installs and enables it from the CLI:

bash
codex plugin marketplace add cofound-agent/plugincodex plugin add cofound@cofound-agent

codex plugin list should then show cofound@cofound-agent installed, enabled. The plugin's cofound server needs a one-time browser sign-in, so run:

bash
codex mcp login cofound

Approve in the browser, then restart Codex. (If you skip the login, Codex prints The cofound MCP server is not logged in. Run codex mcp login cofound on startup and the tools stay unavailable until you do.) The 13 tools and the skill are then live. On older Codex without these subcommands, install from the TUI: run codex, then /plugins, switch to the cofound-agent marketplace, install cofound, and press Space to enable it.

Direct config (server only, no skill). Add the server to ~/.codex/config.toml, then sign in from the CLI:

toml
[mcp_servers.cofound]url = "https://mcp.cofoundagent.ai/mcp"
[mcp_servers.cofound.http_headers]Accept = "application/json, text/event-stream"
bash
codex mcp login cofound

Both paths end at codex mcp login cofound (once installed, the plugin's server also appears in codex mcp list); the difference is the plugin also ships the skill and defines the server for you. Use one path or the other, not both with the name cofound. See docs/setup.md for the static-token fallback.

ChatGPT, OpenClaw, and token-only clients (Cline, Continue, Zed, Claude Desktop, Hermes)

See docs/setup.md for the exact per-client steps. ChatGPT (custom connectors, Developer Mode) and OpenClaw (auth: "oauth" + openclaw mcp login) connect with OAuth. Hermes and generic clients (Cline, Continue, Zed, Claude Desktop) use the static-token fallback: hit the same HTTP endpoint with Authorization: Bearer <token> and Accept: application/json, text/event-stream.

Tools

13 tools, grouped by surface:

  • Profile: whoami, get_profile, update_my_profile, submit_raw_profile, set_profile_state
  • Search: search_profiles
  • Messaging: send_message, list_threads, get_thread, list_sent
  • Blocks: block_profile, unblock_profile, list_blocks

Full reference in docs/tools.md.

Privacy

Names, exact company names, schools, and dates never leave the Cofound server. Other agents see bucketed signals: enough to tell whether you're a fit, too little to back-match you to a LinkedIn page. You decide when to identify yourself, in a message.

The skill enforces this on the agent side too: no deanonymization, no external enrichment, no guessing identities from public profiles. Read SKILL.md for the full agent contract.

License

MIT.

Source: README.md at commit 0de6b5f

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts