MCP Server
Connect AI agents to DealSurface through the Model Context Protocol. Research prospects, map buying committees, and draft outreach through natural conversation.
What is MCP?
The Model Context Protocol (MCP) is an open standard for connecting AI assistants to external tools. The DealSurface MCP server (@dealsurface/mcp-server) wraps the REST API into a set of tools that any MCP-compatible AI agent can use.
When to use MCP vs REST
Use the MCP server when:
- Building an AI agent or conversational workflow
- Working in Claude Desktop or an MCP-compatible client
- You want the AI to decide which tools to call and in what order
- Prototyping a multi-step sales research workflow
Use the REST API when:
- Building a custom integration or script
- You need precise control over every API call
- Integrating with a CRM, dashboard, or automation platform
- Processing data in bulk
Available tools
The MCP server exposes 9 tools, each mapping to a REST API endpoint:
| Tool | REST endpoint | Credits |
|---|---|---|
| list_products | GET /products | Free |
| get_product | GET /products/:id | Free |
| list_prospects | GET /prospects | Free |
| get_prospect | GET /prospects/:ticker | Free |
| search_excerpts | GET /excerpts | Free |
| get_dealmap | GET /dealmap | Free |
| generate_dealmap | POST /dealmap/generate | 0-10 |
| override_stakeholder_role | PATCH /dealmap/node-role | Free |
| craft_outreach | POST /outreach | 1 |
Release notes
0.2.02026-05-21Added optional include_disabled metadata access for list_products and get_product. Operational tools continue to use active products only.
0.1.32026-04-06Added get_dealmap, generate_dealmap, and override_stakeholder_role tools for buying committee mapping. Removed get_leads tool (use get_dealmap instead). Updated craft_outreach for role-aware personalization.
0.1.22026-04-03Improved tool descriptions for clarity.
0.1.12026-03-15Initial public release. Published to npm and MCP Registry.