No install, no Node, no API key in a config file — you approve it in the browser like any other connected app, and it stays up to date on its own.
概览
No install, no Node, no API key in a config file — you approve it in the browser like any other connected app, and it stays up to date on its own. Setup for every client: Nothing here has been switched off and nothing is about to break, so there is no rush — but it will not get new tools, and it is no longer what we point people at. Settings → Connectors → Add → Add custom connector → https://mcp.draftboard.com Then remove the old draftboard entry from your MCP config, and delete the API key you created for it (Settings → API keys) — the hosted connection issues and revokes its own. The hosted server is approved instead of reading DRAFTBOARD_API_KEY from the environment. That means you have to be signed in to Draftboard in a browser on the machine doing the approving. ; that case is not yet covered. The tools are the same. Both surfaces expose the identical set, checked by a test that compares them, so moving is not a trade-off in what your assistant can do.
README
以下为原文 README 节选，完整内容请查看原文。
@draftboard/mcp
⚠️ Superseded — use the hosted server instead
Draftboard now runs the MCP server for you at
https://mcp.draftboard.com. No install, no Node, no API key in a config file — you approve it in the browser like any other connected app, and it stays up to date on its own. Setup for every client: ****This package still works. Nothing here has been switched off and nothing is about to break, so there is no rush — but it will not get new tools, and it is no longer what we point people at.
Moving
# Claude Code claude mcp add --transport http draftboard https://mcp.draftboard.com claude mcp login draftboard # Codex CLI codex mcp add draftboard --url https://mcp.draftboard.com codex mcp login draftboardClaude Desktop: Settings → Connectors → Add → Add custom connector →
https://mcp.draftboard.comThen remove the old
draftboardentry from your MCP config, and delete the API key you created for it (Settings → API keys) — the hosted connection issues and revokes its own.One difference worth knowing before you move
The hosted server is approved in a browser instead of reading
DRAFTBOARD_API_KEYfrom the environment. That means you have to be signed in to Draftboard in a browser on the machine doing the approving. If you run this headlessly — CI, a server, a container with no browser — stay here for now; that case is not yet covered.The tools are the same. Both surfaces expose the identical set, checked by a test that compares them, so moving is not a trade-off in what your assistant can do.
A Model Context Protocol server for the Draftboard Integration API. It lets any MCP-capable agent (Claude, Codex, etc.) work with your Draftboard warm-introduction data — targets, connection paths, ranks, and tags — to answer questions like “who are my best intro opportunities right now?” or “am I already connected to these people?”.
Draftboard maps how your team is really connected to your prospects; this server exposes that data over MCP. API reference: .
Just want to get intros (not build on the API)? Also install the companion
draftboard-introsskill — it teaches your assistant which tool to reach for and how to read the results. This server is only the engine.
Requirements
- Node.js 20+
- A Draftboard Integration API key (Pro/Team plan with API access). Find it in the Draftboard app under Settings → API keys.
Quick start
The server speaks MCP over stdio. Point your client at it and pass the key via env.
Claude Code / Claude Desktop (.mcp.json or claude_desktop_config.json)
{
"mcpServers": {
"draftboard": {
"command": "npx",安装
npx -y github:draftboardco/mcp配置
{
"mcpServers": {
"draftboard": {
"command": "npx",
"args": ["-y", "github:draftboardco/mcp"],
"env": {
"DRAFTBOARD_API_KEY": "db-api_xxxxxxxx"
}
}
}
}