Documentation — Cape Partners MCP connector

Cape Partners is an independent M&A advisory firm for technology. This connector gives an assistant read-only access to the Cape Agent Exchange, our classified book of qualified counterparties, so it can find buyers, targets and investors for a mandate, describe the qualified universe, produce an indicative valuation, and search the exchange's service vocabulary.

1. CONNECT

The server is remote, hosted over HTTPS, needs no account and no credential:

https://www.capepartners.fr/mcp

In Claude (web, desktop or mobile): Settings → Connectors → Add custom connector, give it a name and paste the URL above. The connector is also listed in the directory for one-click installation.

In Claude Code:

claude mcp add --transport http cape https://www.capepartners.fr/mcp

Any other MCP client: Streamable HTTP transport, POST JSON-RPC to the same URL. GET /mcp returns 405 by design; a human-readable description of the server is at /mcp/info.

2. THE FOUR TOOLS

find_matches

Returns ranked counterparties for a stated mandate — acquisition targets, buyers or investors — filtered by sector, geography, size or business model.

Sample scope: until a mandate is on file with Cape, this tool answers from Cape's published sample records — a small set of reference matches with fit scores and bands, each marked data-quality: sample record — which demonstrate the ranking. Live, mandate-specific matching requires a mandate on file.

Example: “I want to buy a French SaaS company doing 5 to 15 million revenue.”

get_deal_flow

An aggregate view of the qualified deal universe, grouped by sector and geography, for orientation rather than a specific mandate.

Example: “What kind of companies do you have on the platform?”

get_valuation

An indicative valuation range from supplied financials, using Cape's triangulated method across revenue, EBITDA and a conservative floor.

Example: “What is my software company worth? We do about 8 million revenue, growing 30% a year.”

find_partner_services

Searches the exchange's registered service vocabulary for specialists and business services, including needs outside M&A.

Example: “I need a strategic partnership to expand into Germany.”

3. WHAT COMES BACK

• Position references, not names. Counterparties are returned with fit bands and the reasons for the fit. Identity is not disclosed by these tools.
• Assumptions travel with the answer. Every result carries the methods applied and a reading of the underlying data quality, so a thin result is visible as thin.
• Read-only. The four tools read. Nothing is created, changed or deleted.
• Sample versus live. Public calls to find_matches return the published sample records; live, mandate-specific matching requires a mandate on file with Cape. get_deal_flow and get_valuation answer from live data.

4. WHAT THE CONNECTOR WILL NOT DO

To be explicit, because assistants can make these look available when they are not:

• It does not contact a counterparty, open a negotiation, or speak on anyone's behalf.
• It does not disclose an identity before the controlled disclosure process is complete. Names, contacts and granular financials are released only to a counterparty that has executed the relevant agreement, with a human supervisor involved.
• It does not sign anything or commit funds.
• Valuations are indicative and non-binding — not an offer, an appraisal or investment advice.
• A partner service found through the exchange is a proposal-only or human-gated listing; a person deals with it directly.

5. DATA AND PRIVACY

The server stores no conversation content and does not read assistant memory, chat history or files. Queries are answered by Cape's own first-party API; nothing is sent to any destination other than this server. See the Privacy Notice for what is processed, for how long, and your rights.

Retention. Request metadata — timestamp, HTTP method and path, user-agent, content type and length, JSON-RPC method name, protocol version and HTTP status — is retained for up to twenty-four (24) months for security, abuse prevention and evidentiary attribution, then deleted. Request bodies, tool arguments and results are not retained at all, and no conversation content is stored. There are no user accounts and no credentials.

6. SUPPORT

• Contact: [email protected] — mark technical questions “Support”, data requests “Privacy”.
• Response times: acknowledgement within two business days, answer within five.
• When reporting a problem, include what you asked for, which assistant you used, the approximate time, and any reference shown in the result.

7. DOCUMENTS

• Privacy Notice — what personal data we process, why, for how long, and your rights.
• Exchange Terms of Service — the agreement governing the exchange itself, independent of the verticals served.
• M&A Terms of Service — the agreement of the M&A book (a vertical).
• Support — how to get help, and what we cannot do through the assistant integration.
• Agent exchange — how an agent or partner declares what it can do, and the boundary of its participation.