Fundra hosts a remote Model Context Protocol server. Connect it to your AI assistant and it can read your funds, portfolio companies, investments, metrics, investor updates, files and people – the same data you see in the app, with the same permissions.

Server URL: https://mcp.fundra.com/mcp

No API key is needed. The server uses OAuth: your client opens a browser window, you sign in to Fundra and approve the connection, and the assistant then acts as you.

The connection inherits your own access rights. Anything you cannot see in Fundra is not visible to the assistant either, and revoking your Fundra access revokes the connection.

Set up

Claude

Claude supports remote MCP servers natively – no local install required.

Open Settings → Connectors (on claude.ai or in the desktop app).
Click Add custom connector.
Name it Fundra and enter the URL https://mcp.fundra.com/mcp.
Click Connect, sign in to Fundra, and approve the request.

Claude Code

claude mcp add --transport http fundra https://mcp.fundra.com/mcp

Then run /mcp inside Claude Code and authenticate when prompted.

ChatGPT

Open Settings → Connectors → Advanced → Developer mode and enable it.
Go back to Connectors and click Create.
Name it Fundra, enter https://mcp.fundra.com/mcp as the MCP server URL, and choose OAuth authentication.
Click Create, then sign in to Fundra and approve the request.

Cursor

Add the server to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):

{
  "mcpServers": {
    "fundra": {
      "url": "https://mcp.fundra.com/mcp"
    }
  }
}

Open Settings → MCP and click Login next to the Fundra server to authenticate.

Other clients

Any client that speaks streamable HTTP with OAuth can connect to https://mcp.fundra.com/mcp directly. For clients that only support local stdio servers, use mcp-remote as a bridge:

{
  "mcpServers": {
    "fundra": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.fundra.com/mcp"]
    }
  }
}

What the assistant can do

The server exposes two tools:

Tool	Purpose
`fund_analyst`	Queries your Fundra data. The assistant can pull of bespoke analyses that traverse Fundra data, calculate IRR across arbitrary groups and retain internal consistency of Fundra metrics without hallucinations.
`select_account`	Picks which workspace to work in, if your login has access to more than one.

Rather than exposing one tool per API endpoint, fund_analyst gives the assistant the whole Fundra API as a typed interface it can call, filter and aggregate in a single step. That means fewer round trips and answers that are computed rather than guessed – a question like "which companies are above 3x MOIC?" is one call, not twenty.

Available data mirrors the API: funds, portfolio companies, companies, investments, metrics and KPIs, investor updates, meeting notes, files, people and FX rates.

Because the assistant reads figures that Fundra has already calculated – IRR, MOIC, margins, growth – the answer to "what's our IRR by sector?" uses the same logic as the number in your LP report. You get an arbitrary cut of the portfolio without a second, differently-calculated version of the truth.

Selecting a workspace

If your account has access to several workspaces, ask the assistant to switch:

Switch to the Acme Ventures workspace

The choice is remembered for the rest of the session. Without an explicit selection, the first workspace on your login is used.

Example prompts

Summarise how our portfolio performed last quarter, by fund.
What's our IRR by sector? And by geography?
Which portfolio companies have not sent an investor update in the last 90 days?
List my companies with their latest ARR and runway, sorted by MOIC.
Compare invested capital and FMV across all funds in EUR.
What were the key risks raised in the last three board meetings for Acme?
Draft an LP update section on our top five holdings, using the latest KPIs and investor updates.

Troubleshooting

The client cannot connect. Confirm the URL ends in /mcp and that your client supports remote servers; otherwise use the mcp-remote bridge above.

Authentication loops or fails. Sign in to Fundra in the same browser first, then retry the connection. Removing and re-adding the connector clears a stale token.

The assistant answers about the wrong workspace. Ask it change the workspace to the preferred one.

No data comes back. The connection uses your own permissions – check you can see the same records in the Fundra app.

Any questions? Drop us a note on Slack, in the live chat or hello@fundra.com.

MCP Server