Carta MCP server and Claude connector: what it does, what it can change, how to connect
Carta hosts a remote MCP server behind its Claude connector. Its three plugins read and write, and one can issue equity. You sign in with OAuth. Verified 21 Oct 2026.
- Official MCP server + plugins · read & write (hosted)
- Claude connector · read & write (via plugins)
- Hosting
- Remote HTTP hosted by Carta: https://mcp.app.carta.com/mcp. Server source isn't public; plugins are at github.com/carta/plugins (Apache-2.0).
- Auth
- OAuth with your Carta login. Carta says Claude sees only the data your Carta account can already view; it publishes no scope names.
- Read / write
- Read & write. Most skills query and report, but Cap Table can issue securities, Investors can save or finalise valuations, publish KPI corrections and send data and Fund Admin requests, and CRM adds and updates records.
- Works with
- Claude.ai, Claude Desktop, Claude Code, ChatGPT Work (Codex) Desktop, any MCP client that supports HTTP
- Plan requirement
- A Carta account; Carta documents setup for Claude Pro, Max, Team and Enterprise. Investors data needs firm data sharing enabled by a Carta admin.
- Last changed
- 2026-10 (plugin versions 6.97.21 Cap Table, 6.105.10 Investors, 1.18.3 CRM in the public repo; patch versions change often)
- Verification
- Verified 21 Oct 2026 by theFinanceStack · confidence: high
What can an agent do with Carta through MCP?
An agent can query cap tables, fund data and CRM records, and, through specific plugin skills, change Carta: issue securities, save or finalise valuations, correct KPIs, send data and Fund Admin requests and edit CRM records.
Where it runs
| Option | Tools | Notes |
|---|---|---|
| Claude directory listing | 9, mostly discovery and fetch tools: welcome, discover, fetch, list_contexts, set_context, list_accounts, get_current_user, cap_table_chart, cap_table_healthcheck | Plugin skills reach further commands through them. |
| Carta's public repo (plugin skills) | 20 Cap Table, 22 Investors and 27 CRM skills | Carta describes the Investors plugin as write-capable. |
What happens when it writes
Each write path has its own gate.
| Action | What happens |
|---|---|
| Issue securities | Asks for one confirmation, then issues. Carta's skill calls this irreversible. |
| Option grants that need board consent | Held as drafts until the board approves. |
| Routine valuation changes | Saved without asking and shown afterwards. |
| Finalise or delete a valuation | Waits for an explicit yes, because Carta says neither can be undone. |
| Data collection and Fund Admin requests | Confirmed before anything is sent. |
| KPI corrections | Staged in the portfolio analytics app. Written to Carta when the user clicks Publish N changes. |
| CRM add and update | The skills collect the fields, then write. Carta documents no separate confirmation step for them. |
Money
No documented tool moves money.
Can
- Query ownership, stakeholders, SAFEs, grants, vesting, 409A history and rounds (Cap Table)
- Issue certificates, option grants and profits interest units, or save drafts (Cap Table)
- Query NAV, partner capital, journal entries and portfolio financials with read-only SQL (Investors)
- Build Excel budgets and consolidating financial reports (Investors)
- Save, finalise or delete portfolio valuations, publish KPI corrections, send data requests (Investors)
- Open, track and reply to requests that the Carta Fund Admin team acts on (Investors)
- Search, add and update investors, companies, contacts, deals, notes and fundraisings (CRM)
Cannot
- See data the signed-in Carta user cannot already view (per Carta)
- Issue RSUs, SARs, warrants, SAFEs, convertibles or custom terms; the issuance skill routes those to the Drafts UI in Carta
- Fix an issued profits interest unit; per Carta, PIU corrections are made in the Carta app
- Return Investors data unless the firm has data sharing enabled (per Carta)
- Release payments or move money (no such tool documented)
What access does it get?
One OAuth sign-in as a Carta user, limited to what that user can view in Carta. Carta publishes no scope names and no read-only option.
| Where | Scopes and permissions (as documented) | Admin requirement |
|---|---|---|
| Carta MCP server (mcp.app.carta.com) with plugins | Not documented by the vendor as named scopes. OAuth with Carta credentials; access limited to data the account can already view. list_contexts and set_context switch between firms the user can access. | A Carta admin enables firm data sharing for Investors data. Claude Team/Enterprise: an Owner adds the connector and sets how each plugin is distributed. |
| Claude directory connector (claude.com/connectors/carta) | Not documented by the vendor. The listing says sign-in is required and points to the same server URL. | Claude Team/Enterprise: an Owner adds it; members then click Connect and log in to Carta. Pro/Max: each user adds it. |
How do I connect it?
Add the Carta connector, sign in to Carta, then install only the plugins you need; other clients add https://mcp.app.carta.com/mcp as an HTTP server.
- Team/Enterprise: an Owner opens Organization settings › Connectors › Add, searches Carta and adds it; then in Organization settings › Plugins (Anthropic & Partners) sets each Carta plugin to Installed by default or Available in catalog.
- Members go to Customize › Connectors › Carta › Connect and log in to Carta.
- Pro/Max: Customize › Connectors (+) › Carta › Connect, then Personal Plugins (+) › Browse plugins › Partners tab and install each plugin you want.
- Install only the plugins you need. Carta documents no scope narrowing, so the Owner's controls are each plugin's distribution setting and each member's Carta role. For example, set Cap Table, which can issue equity, to Available in catalog or leave it out.
Directory listing: https://claude.com/connectors/carta. Members who see permission errors need an Owner to finish the org setup. Carta's GitHub marketplace route (Option C) also offers a Required distribution and a Sync automatically toggle, which installs new plugin versions, including updated hook programs, as Carta publishes them.
What should a finance team watch for?
Some Carta skills make changes that cannot be undone, such as issuing securities or emailing portfolio companies, so decide which plugins each person gets before connecting.
- Issuing equity takes one confirmation click, and Carta's skill calls the write irreversible; signatories are then notified. Option grants that need board consent stay as drafts until the board approves. Check every row against board approvals first. Carta lists a separate skill for amending issued certificates and option grants.
- The valuations skill saves routine changes without asking first and shows a before-and-after summary, so review it each time. Finalising or deleting a valuation needs an explicit yes, because Carta says neither can be undone.
- Data collection requests email people outside Carta and, per Carta, cannot be recalled. Fund Admin requests open work for Carta's Fund Admin team; both ask for confirmation before sending.
- Carta doesn't document a read-only mode or scope narrowing. Least privilege comes from the Carta user's role, firm data sharing, and which plugins an Owner distributes.
- Each Carta plugin installs Claude Code hooks that run small compiled Carta programs at session start, on each prompt and before each Carta skill or tool call. Carta's READMEs say the plugins collect telemetry covering session context, model configuration and plugin activity. Carta ships the Go source and a SHA256SUMS file with a verify-checksums.sh script, so IT can check the programs before rolling plugins out.
- CRM notes, deal records and portfolio documents are untrusted text: an injected instruction could push an agent to update a record or start an issuance. Routine valuation saves and CRM updates have no confirmation step of their own, so in Claude set Carta's tools to ask for approval each time. The Claude listing says to "Only use connectors from developers you trust."
- Carta's guide points to Carta's and Anthropic's privacy policies for retention and makes no training statement.
- Carta documents no rate or record limits, and doesn't document which Carta subscriptions each plugin needs.
How could finance teams and accounting firms use it?
Query skills fit ownership, fund and reporting questions. The write skills fit preparing issuances, valuations and CRM updates that a person checks before confirming.
Inside a company
- Answer ownership, option pool and fully diluted questions for a board pack without exporting a cap table.
- Check when the 409A expires and which grants vest soon.
- Model a priced round or SAFE conversion before a financing, then compare it with counsel's numbers.
- Prepare a batch of approved option grants as drafts for the equity administrator to review and issue in Carta.
At an accounting firm
- Pull NAV, partner capital and journal entries into consolidating reports for a fund client.
- Build a management company budget from prior-year actuals.
- Pull Form ADV Schedule D and regulatory AUM data for the adviser's compliance lead to check before filing.
- Draft portfolio data requests and have the fund controller approve each send.
Whatever the use, keep a person approving anything that changes the cap table, a valuation or someone's inbox, and treat AI-built reports as drafts until they tie to Carta.
Want Carta connected to Claude for your team?
We set up role-limited Carta access, choose which plugins each person gets, and add a review step before anything changes your cap table or fund records. Fixed fee.
Book a 30-minute setup callChange log
| Date | Change | Source |
|---|---|---|
| 2026-10-21 | Setup guide re-checked; same server URL | docs.carta.com/api-platform/guides/guides/claude-mcp-setup/ |
| 2026-10 | Public plugin repo at Cap Table 6.97.21, Investors 6.105.10 and CRM 1.18.3 as of 21 Oct 2026; Investors described as write-capable; Cap Table includes an issuance skill; each plugin ships telemetry hooks | github.com/carta/plugins |
| 2026-05 | Carta connector added to the Claude directory (9 tools listed, Anthropic verified) | claude.com/connectors/carta |
FAQ
Is this official?
Yes. Carta hosts the server, documents setup on docs.carta.com and publishes the plugins on GitHub; the Claude listing is published by Carta and marked Anthropic verified.
Is it free?
Carta doesn't document a separate charge. You need a Carta account and a Claude plan that allows connectors (Carta documents Pro, Max, Team and Enterprise).
Does it change data in Carta?
Yes, through certain skills: it can issue securities after one confirmation, save or finalise portfolio valuations, publish KPI corrections, send data and Fund Admin requests and add or update CRM records. Query skills only read.
Is my data used to train models?
Carta's setup guide doesn't say. It points to Carta's and Anthropic's privacy policies, and the plugins collect telemetry. Read both companies' terms before connecting.
Can my accountant use it on my behalf?
Carta doesn't document this. The connection acts as whoever signs in, so an accountant needs their own Carta access, and their role sets what the agent can do.
Sources
- Carta Developer Platform: Claude plugins setup
- GitHub: carta/plugins (READMEs and skill files)
- GitHub: Carta Investors hooks README (telemetry hooks and binary checks)
- Claude directory: Carta connector
- Claude plugin marketplace: carta-cap-table
- Carta: AI connector page (not reachable on 21 Oct 2026)
- mcpservers.org: Carta remote MCP listing (not reachable)
Verified by theFinanceStack, 21 Oct 2026. Vendor list on the CFO Software Market Map courtesy of Jason Staats; AI connectivity data by theFinanceStack. Not tax, compliance or financial advice.