How a Private Equity Firm Uses Claude With Meridian MCP

A private equity firm and Meridian customer connected Claude directly to their live deal data through Meridian MCP, and the first thing that changed was the copy-paste routine.

Before the connection, an associate kept a browser tab open to export deal records out of the CRM, paste them into a prompt, and redo it every time the pipeline moved. After connecting Meridian MCP to Claude, repetitive tasks that once took hours now happen automatically.

What is MCP?

Model Context Protocol is the open standard Anthropic introduced for connecting AI agents to the systems where data lives. It’s what lets an MCP-enabled AI platform like Claude query Meridian directly instead of waiting for a person to paste in fragments of the CRM record. 

With Meridian MCP, deal teams never have to leave the chat with their preferred AI model.

3 Workflows the firm built with its Meridian MCP connection

The firm built three workflows on one MCP connection to Meridian: a daily pipeline briefing, meeting and broker call prep, and IC memo drafting. None required new features from Meridian, and each automates a task the team used to do by hand against its old CRM.

Workflow 1: A daily pipeline briefing that lands before the day starts

Each morning, Claude sweeps every stage of the firm's pipeline in Meridian and emails the team a consolidated summary. It is the firm's highest-frequency use by a wide margin, replacing a manual pipeline check with a briefing that is already waiting when people sit down.

Workflow 2: Meeting and broker call prep pulled straight from the record

Ahead of a meeting, the team asks Claude to pull deal history, prior interactions, and notes on a target directly from Meridian. Full context arrives with the query, so no one spends the half hour before a broker call assembling it by hand.

Workflow 3: IC memos drafted from CRM data and deal documents together

The firm has Claude draft investment committee memos from Meridian deal records alongside CIM and QoE materials. The draft pulls structured CRM data and unstructured deal files in the same pass, so the first version exists before an analyst starts formatting.

The compounding benefits of Meridian MCP

None of these three workflows required new features from Meridian. The firm built all three on top of an MCP connection to data that already lived in their CRM. 

That is exactly why we built Meridian MCP as an open data layer rather than a closed assistant. A team can point Claude at diligence, another model at drafting, and Scout AI at sourcing inside Meridian, all reading the same system of record with the firm's permissions intact. The workflows built on top of that access are up to the firm, not up to Meridian's product roadmap

See What Meridian MCP Can Do For Your Firm

Your deal data becomes readable by the AI tools your team already uses, with your firm's permissions intact. See how Meridian works.

Frequently asked questions

What is Meridian MCP?

Meridian MCP is a hosted server that lets approved AI agents like Claude and ChatGPT read a firm's deal data through one secure endpoint. It runs on Model Context Protocol, the open standard Anthropic introduced for connecting AI agents to external systems. Firm permissions stay intact, so an agent only sees what the user is allowed to see.

Can Claude read my CRM data directly?

Yes. Through Meridian MCP, Claude queries your live deal records, interactions, notes, and documents in Meridian without exports or copy-paste. Context travels with the question, so answers reflect the current state of the pipeline rather than a snapshot pasted into a prompt.

What can a deal team do with Claude connected to Meridian?

Teams use it for recurring work like a daily pipeline briefing, meeting and broker call prep, and drafting IC memos from deal records and documents together. Because the workflows run on data already in the CRM, a firm can build its own without waiting on new product features.

Do these workflows require custom development from Meridian?

No. The firm in this post built all three on the standard MCP connection, using data that already lived in Meridian. The output is only as complete as the records the firm keeps current, so the effort goes into data hygiene rather than integration work.