# Inside the Carta CRM MCP server: From basic tools to a platform for building **Author:** Ihar Valodzin **Read time:** 5 minutes **Published date:** July 1, 2026 Learn how the Carta CRM MCP server uses the Model Context Protocol to create a programmable substrate for AI agents. Build reliable, production-grade workflows. ## Contents - [Inside the Carta CRM MCP server: From basic tools to a platform for building](/content/blog/inside-the-carta-mcp-server/#inside-the-carta-crm-mcp-server-from-basic-tools-to-a-platform-for-building/index.html) - [The tool composition architecture](/content/blog/inside-the-carta-mcp-server/#the-tool-composition-architecture/index.html) - [Tier 1: Primitive read/write tools](/content/blog/inside-the-carta-mcp-server/#tier-1-primitive-read-write-tools/index.html) - [Tier 2: Aggregation and cross-entity reasoning tools](/content/blog/inside-the-carta-mcp-server/#tier-2-aggregation-and-cross-entity-reasoning-tools/index.html) - [Tier 3: Platform and meta-tools](/content/blog/inside-the-carta-mcp-server/#tier-3-platform-and-meta-tools/index.html) - [What firms could build](/content/blog/inside-the-carta-mcp-server/#what-firms-could-build/index.html) - [Origination Intelligence Agent](/content/blog/inside-the-carta-mcp-server/#origination-intelligence-agent/index.html) - [Relationship Coverage Assistant](/content/blog/inside-the-carta-mcp-server/#relationship-coverage-assistant/index.html) - [The architectural principle](/content/blog/inside-the-carta-mcp-server/#the-architectural-principle/index.html) - [Getting started with the Carta CRM MCP](/content/blog/inside-the-carta-mcp-server/#getting-started-with-the-carta-crm-mcp/index.html) **Model Context Protocol (MCP) is an open standard for connecting AI models to external tools and data sources.** Think of it as a standardized interface between an AI agent and the systems it needs to act on. Before MCP, integrating an AI model with your CRM may have meant custom API wrappers and brittle code that broke whenever something changed. Every team that wanted an AI-powered workflow might have been rebuilding the same plumbing. MCP solves this at the protocol layer. You define a set of tools—functions with typed schemas—the AI can discover and invoke. The AI figures out which tools to call, in what order, and with what parameters. You get composable, auditable, model-agnostic workflows without rebuilding the integration every time you swap models or change your workflow. The [**Carta CRM**](/content/fund-management/deal-crm/index.html) MCP server exposes the entire CRM as a set of these tools. That’s the foundation. But what’s interesting is not just that the tools exist, but how they’re layered. ## The tool composition architecture The Carta CRM MCP server is organized in three progressive tiers. Each tier builds on the one below it. Together they turn a CRM into a programmable substrate for AI workflows. ### **Tier 1: Primitive read/write tools** The foundation is atomic operations: one entity, one action. These tools handle the basic create, read, update, and delete (CRUD) operations across every entity in the CRM: ``` search_contacts create_contact update_contact fetch_contact_by_id delete_contact search_companies create_company update_company fetch_company_by_domain fetch_company_by_id delete_company search_deals create_deal update_deal fetch_deal_by_deal_id delete_deal create_note update_note fetch_note_by_id link_note unlink_note delete_note ``` Each tool has a typed input schema. `search_contacts` takes query parameters—name, email, list membership, custom fields. `create_deal` takes a structured deal object. The AI doesn’t need to know your API; it just needs to know the schema, and the MCP tool definition carries that schema. These primitives are what most CRM integrations stop at: Point an AI at your CRM, give it read and write access, and call it done. That’s useful, but limited. The AI is executing individual operations, not reasoning across your data. Tier 1 is necessary, but it’s not sufficient. ### **Tier 2: Aggregation and cross-entity reasoning tools** The second tier is where the analytical capability lives. ``` aggregate_deals aggregate_companies aggregate_investors aggregate_fundraising fetch_contact_interactions_by_emails list_interactions_by_domain get_deal_stage_history enrich_person ``` These tools do something Tier 1 can’t: They return structured summaries across multiple records, apply filters at scale, and surface relationship context that spans entity boundaries. `aggregate_deals` returns a filtered, aggregated view of your deal pipeline: sector breakdowns, stage distributions, and time-in-stage metrics. The AI can ask: “What does our current healthcare pipeline look like above $100 million in revenue?” and get a structured answer without querying hundreds of individual records. `fetch_contact_interactions_by_emails` is particularly powerful. It returns the full interaction history for a set of contacts—emails, meetings, notes—in a single call. An AI agent drafting outreach can pull the last six months of context on a relationship before generating a single word. `list_interactions_by_domain` does the same at the company level. Every touchpoint your firm has had with anyone at a target company, surfaced in one tool call. `enrich_person` reaches outside your CRM entirely—it pulls third-party professional data and returns it in the same structured format, so enrichment is composable with the rest of your workflow. This tier is what enables the difference between an AI that can look up a record and an AI that can reason about your relationships. ### **Tier 3: Platform and meta-tools** The third tier is the one most people miss…and the one that turns the MCP connector into something closer to a platform. ``` get_platform_how_to_guide product_support_hotline get_contact_fields get_company_fields get_deal_fields get_contact_custom_fields get_company_custom_fields get_deal_custom_fields get_deal_pipelines_with_stages get_fundraising_stages ``` The how-to guide and support tools are not for end users. They’re for AI agents. `get_platform_how_to_guide` returns structured documentation about how to accomplish specific workflows inside the CRM. When an AI agent is building a multi-step workflow—say, a deal origination pipeline that creates records, links interactions, and scores coverage—it can call this tool to understand the right sequence of operations. The AI doesn’t need to guess; it can look it up. `product_support_hotline` is similar: an AI can ask questions about CRM behavior and get structured answers back, mid-workflow. This makes agents dramatically more reliable—they can handle edge cases and ambiguous states without failing or asking the human for help. The schema introspection tools—`get_contact_fields`, `get_company_custom_fields`, etc.—expose your exact CRM schema dynamically. This matters because every firm’s custom field configuration is different. An AI agent that reads your schema before writing data will map fields correctly without being hardcoded to your setup. The same agent code works across every Carta CRM tenant. `get_deal_pipelines_with_stages` and `get_fundraising_stages` do the same for your workflow configurations. An agent building deal tracking logic can discover your exact pipeline structure at runtime rather than having it hardcoded. Together, Tier 3 tools give AI agents the context to operate reliably on CRM data they’ve never seen before—and to ask for help when they’re uncertain. ## What firms could build The layered architecture model isn’t theoretical. Here are two examples of what could run on it: ### Origination Intelligence Agent A mid-market PE firm built an origination agent that monitors an inbound deal flow list and scores every new opportunity against historical pattern data. The agent uses `aggregate_deals` to pull closed and passed deals by sector, size, and geography. When a new company is added to the pipeline list, the agent calls `list_interactions_by_domain` to check for any prior interaction history, `enrich_person` to pull current leadership data, and `aggregate_deals` again to benchmark the opportunity against comparable deals the firm has evaluated. The output was a structured deal memo pre-populated in the CRM, with a coverage score, comp set, and a recommended first contact, before a human has read the IM. ### Relationship Coverage Assistant A growth equity firm with a large banker network needed to systematically track coverage quality—not just who they knew, but the recency, depth, and deal conversion rate of each relationship. The agent runs weekly. It calls `fetch_contact_interactions_by_emails` across the banker contact list, pulls `get_deal_stage_history` to map which bankers sourced which deals, and uses `aggregate_deals` to calculate conversion rates by source. It writes coverage scores back to custom fields via `update_contact`. Come Monday morning: a ranked coverage dashboard, updated automatically, with flagged relationships that have gone cold. ## The architectural principle There’s a design philosophy behind the three-tier structure that’s worth naming explicitly. Most CRM AI integrations are built to answer one question: _What can the AI see?_ The Carta CRM MCP server is built to answer a different one: _What can the AI do, and how reliably can it do it at scale?_ Tier 1 gives access. Tier 2 gives analytical depth. Tier 3 gives the AI the context to operate correctly—on your specific schema, in your specific workflow—without brittle hardcoding. The result is a connector that functions as a platform firms can build real production workflows on top of, not just prototype against. ## Getting started with the Carta CRM MCP **The Carta CRM MCP server is available to all customers. You can connect it to Claude, GPT, or any MCP-compatible agent framework.** Full tool documentation, schema references, and quick-start guides are in the [Carta CRM developer docs](https://docs.carta.com/crm/docs/getting-started). If you’re building a custom workflow and want to talk through the architecture, [book time with the team](/content/demo/deal-crm/?ir=blog/index.html). **Author:** Ihar Valodzin Ihar Valodzin leads the Carta CRM product, a deal-winning platform designed to help investment firms centralize their pipeline, manage contacts, and close faster. Prior to building Carta CRM, he spent several years in private equity at Mayfair Equity Partners and BC Partners, as well as strategy consulting at Bain & Co.