Investor portal APIs and MCP servers: what an LP can actually use
Many investor portals now advertise an API or an MCP server. The question for an investor is narrower: can you, as the LP, get credentials? This guide sorts the 63 portals in the open registry by channel and by who each interface is for.
Four ways data leaves an investor portal
An investor portal holds the documents and figures a fund manager shares with its investors: capital call notices, distribution notices, capital account statements, quarterly reports and tax documents. There are four common routes for getting that data out without a person logging in and downloading files.
- API. A documented interface your own software calls, usually over REST with a key or OAuth token. It returns structured data and files on request. It is the most precise channel, and the one with the most rules about who gets credentials.
- MCP server. The Model Context Protocol is an open standard that lets AI assistants call tools on a remote system. A portal's MCP server lets an assistant such as Claude or ChatGPT sign in as a user and query that user's data. It is not a bulk feed. It answers questions and can fetch documents, within the signed-in user's permissions.
- SFTP. A file transfer server where files are dropped on a schedule. It suits back-office pipelines that load statements into an accounting or reporting system. It is usually set up per client, not self-serve.
- Email feeds. Notification emails when a new document is posted. The registry counts below show how often they are recorded. They tell you something changed, but they often link back to the portal rather than carry the document.
The registry records a status for each channel on every portal. The table below counts them across all 63 entries. Unknown means nobody has checked yet, not that the channel is absent.
| Channel | Available | Beta | Partner only | Planned | Not offered | Unknown |
|---|---|---|---|---|---|---|
| API | 6 | 0 | 24 | 1 | 6 | 26 |
| MCP server | 7 | 4 | 6 | 0 | 17 | 29 |
| SFTP | 0 | 0 | 3 | 0 | 6 | 54 |
| Webhooks | 2 | 0 | 1 | 1 | 6 | 53 |
| Email notifications | 25 | 0 | 0 | 0 | 0 | 38 |
The key question: who is the API for?
An API listed as available does not mean an investor can use it. Much portal software is bought by the fund manager (the GP) or the fund administrator, and the API exists so that they can integrate the portal with their CRM, fund accounting or data warehouse. The investor sees the portal from the other side, as an invited user.
The registry captures this in the access.api.audience field, which lists who may obtain credentials: lp, gp, fund-admin or partner. Only an audience that includes lp means an investor can request keys for their own data. The status partner-only means the API exists but requires a commercial agreement with the vendor. That agreement is almost always held by the GP, the administrator or an integration partner, so for an LP a partner-only API is effectively GP-side. The guide partner-only portal access explained covers what that means in practice.
Portals with an API marked available or beta
6 portals in the registry list an API as available or beta. They split by audience as follows.
Usable by investors (1)
The audience includes LPs. Check the portal entry for plan requirements: an investor-side API can still require a paid subscription.
| Portal | Category | API | Audience | Auth | Difficulty |
|---|---|---|---|---|---|
 Arch | Reporting platform | Available | LP, Fund admin, Partner | JWT, OAuth 2 client credentials | 2 / 5 |
GP or owner side only (4)
The audience does not include LPs. These APIs serve the firm that licenses the software, its administrator or integration partners. A family office that is itself the licensee of a platform can use that platform's API for its own data, but an investor invited into someone else's portal cannot.
| Portal | Category | API | Audience | Auth | Difficulty |
|---|---|---|---|---|---|
 Addepar Client Portal | Reporting platform | Available | Partner, Fund admin | Basic, OAuth 2 authorization code | 3 / 5 |
 Digify Data Room | Data room | Available | GP | Basic | 4 / 5 |
 Papermark | Data room | Available | GP | API key, OAuth 2 authorization code | 2 / 5 |
 Securitize | Marketplace | Available | Partner, GP | OAuth 2 authorization code, API key | 3 / 5 |
Audience not recorded (1)
The API is listed, but the registry does not yet record who may obtain credentials.
| Portal | Category | API | Audience | Auth | Difficulty |
|---|---|---|---|---|---|
| DDatasite Diligence | Data room | Available | Not recorded | API key, Other | 3 / 5 |
A further 24 portals list an API as partner-only, of which 4 name LPs in the audience (Backstop Client Portal, Chronograph LP, MSCI Private i (Burgiss) and S&P Global iLEVEL). For 26 portals the API status is unknown. The full registry of investor portals lists every entry with its channel statuses.
Portals with an MCP server
17 portals in the registry record an MCP server: 7 available, 4 in beta and 6 partner-only. Endpoint and authentication are shown where the vendor or a source has published them. Where they are not published, the registry says so.
| Portal | MCP | Endpoint | Auth | Maintainer |
|---|---|---|---|---|
| Addepar Client Portal | Beta | https://mcp.addepar.com/ | OAuth 2 | Vendor |
 Allocate | Partner only | https://mcp.allocate.co/api/mcp | Other (sign-in) | Vendor |
 Altvia ShareSecure | Partner only | Not published | Not recorded | Vendor |
 AngelList (Venture) | Available | https://mcp.angellist.com/mcp | OAuth 2 | Vendor |
 Ansarada Data Room | Partner only | Not published | Not recorded | Vendor |
 CAIS | Beta | Not published | Not recorded | Vendor |
 Carta LP Portal | Available | https://mcp.app.carta.com/mcp | OAuth 2 | Vendor |
 Cash Flow Portal | Partner only | Not published | Not recorded | Vendor |
| CChronograph LP | Available | https://ai.chronograph.pe/mcp | Other (sign-in) | Vendor |
| DDatasite Diligence | Partner only | Not published | Not recorded | Vendor |
 Dropbox DocSend Spaces (data rooms) | Beta | https://docsend.com/mcp | OAuth 2 | Vendor |
 Ideals Virtual Data Room | Available | Not published | Not recorded | Vendor |
 Juniper Square Investor Portal | Beta | Not published | Not recorded | Vendor |
| Papermark | Available | https://mcp.papermark.com/mcp | OAuth 2, API key | Vendor |
 S&P Global iLEVEL | Partner only | Not published | Not recorded | Vendor |
| Securitize | Available | https://mcp.securitize.io | None | Vendor |
 Vauban (Carta Fund Administration, UK/EU) | Available | https://mcp.app.carta.com/mcp | OAuth 2 | Vendor |
An MCP server inherits the permissions of the account that signs in. Whether that account can be an investor depends on the vendor. Most entries describe a server for the firm's own users.
What the vendor MCP servers cover
Short summaries from the registry notes, in no particular order. Status is shown next to each name.
- Addepar Client Portal (Beta): The registry notes an official server marked closed beta in vendor documentation, with sign-in through an Addepar account and tools for private fund cash movements and upcoming capital activity. It is aimed at advisor firm users; end-client access is not stated.
- Papermark (Available): A vendor server, hosted with OAuth and also published as an npm package. The registry notes version 0.1.0, described as alpha, with tools for data rooms, documents, links and visitor analytics. It acts as the data room owner, not as a visitor.
- AngelList (Venture) (Available): A read-only vendor server with tools for capital accounts, capital calls, distributions and documents. The registry notes it is available to GPs and their teams only, and that LP use cases are not yet supported.
- Chronograph LP (Available): A vendor server with query, entity search, commitment history and exposure tools. Chronograph LP is an LP-side monitoring platform where the LP is the customer, so here the server is for the investor organisation.
- Carta LP Portal (Available): A vendor remote server that signs in with existing Carta credentials. The registry notes that fund performance data is mentioned, documents and capital calls are not, and LP coverage is unconfirmed.
- Dropbox DocSend Spaces (data rooms) (Beta): A vendor server in beta for DocSend account users on certain plans, enabled by an admin. Use by people who only view a shared space is not stated.
- Juniper Square Investor Portal (Beta): A vendor server in beta with select customers, with read-only tools for contacts, accounts, positions, documents and transactions. The registry records it as GP-side only.
- Securitize (Available): Recorded from a third-party profile as a public server with five tools. The registry notes this is not verified against vendor documentation.
The pattern across these entries: MCP servers in this market are new, most dated entries in the registry are from 2026, and they are built first for the people who operate the portal. Investor-side MCP access is explicitly ruled out in some entries and not stated in most others.
SFTP and email feeds
3 portals in the registry record an SFTP channel. In each case the notes describe an arrangement for specific clients or for administrators posting files, rather than a self-serve investor feature.
| Portal | SFTP | Registry note |
|---|---|---|
| Arch | Partner only | Earlier arch.co site: 'delivers data to downstream systems via API integrations, SFTP dropoffs, flat files, or Open Data Program' (not on current arch.com page). |
| Carta LP Portal | Partner only | Only for the separate Carta LP Portfolio Analytics product (formerly Accelex). |
| Juniper Square Investor Portal | Partner only | Inbound only, for administrators and GPs posting statements into Juniper Square. |
Email notifications are recorded as available for 25 portals. Webhooks, a machine-readable alternative, are recorded as available for 2 portals (Digify Data Room and Securitize). For a practical approach to turning notification emails into structured records, see how to automate capital call and distribution notices.
Where the open protocol fits
An LP with commitments to many funds deals with many portals, each with its own login, MFA and, at best, its own API. The Open Investor Portal Protocol (OIPP) is a draft open specification for a small, read-only API that any portal can implement: accounts, documents, capital calls, distributions, capital account statements and change notifications, with payloads aligned to ILPA templates.
The design gives the investor one identity across portals. The investor generates a key pair locally and registers only the public key. They link that identity to each portal account they already hold, and then sign requests to each portal directly. No passwords, tokens or portal data pass through OpenInvestorPortal. A local MCP server can sit on top, so the same investor-side assistant works across every portal that implements the protocol.
OIPP is a proposal, not an industry standard. No portal in the registry reports OIPP support yet. It does not compete with vendor APIs for GP-side integration. It addresses the gap the tables above show: few interfaces are issued to investors.
A practical approach for LP operations teams
- List the portals you log in to and look each one up in the investor portal registry.
- Where the API audience includes LPs, ask the vendor for credentials and check plan requirements.
- Where the API is GP-side or partner-only, ask the fund manager or administrator whether they can enable a data feed, SFTP drop or MCP access for your account.
- Where nothing programmatic exists, use notification emails as the trigger and download documents through the portal, within its terms.
- If you know an entry is wrong or out of date, submit a correction so the next team benefits.
Frequently asked questions
Is there an investor portal API that an LP can use directly?
In the registry, 1 portal lists an available or beta API whose audience includes LPs: Arch. The other 5 available or beta APIs are issued to GPs, fund administrators, account owners or commercial partners, or their audience is not recorded.
What is the difference between an API and an MCP server?
An API is a documented interface that your own code calls to fetch data, such as documents or capital account balances. An MCP server is an interface built for AI assistants: an MCP client such as Claude or ChatGPT connects to it, signs in as a user and calls the tools it offers. Both are only useful to an investor if the investor can obtain credentials.
What does partner-only mean for a portal API?
In the registry, partner-only means the interface exists but requires a commercial agreement with the vendor. In practice that agreement is usually signed by the fund manager, the fund administrator or an integration partner, not by an individual LP. The audience field records who may obtain credentials.
Can an LP use a vendor MCP server to read their own fund documents?
Usually not yet, or not confirmed. 17 portals in the registry record an MCP server, but most registry notes describe access for GP teams, advisors or account users, and several state that investor or viewer access is not documented. Check the registry entry for each portal.
Is SFTP still used for fund reporting data?
The registry records SFTP for 3 portals, and for 54 portals it is unknown. Where SFTP exists it is typically arranged per client or used by administrators to post statements, not offered as a self-serve investor feature.
How does the Open Investor Portal Protocol relate to vendor APIs?
OIPP is a draft open specification for a small, read-only investor API that any portal can implement, with the investor authenticating with their own key. It does not replace a vendor API. No portal in the registry reports OIPP support yet.
Sources
- OpenInvestorPortal registry entries in
registry/portals/, schema inschema/portal.schema.json, difficulty ratings inresearch/assessments.json. Each portal page lists its own sources. - https://angellist.com/link
- https://arch.co/client-api/api-docs/
- https://claude.com/connectors/addepar
- https://claude.com/connectors/carta
- https://developer.datasite.com/
- https://developer.digify.com/
- https://developers.addepar.com/docs
- https://docs.carta.com
- https://docs.carta.com/api-platform/docs/carta-mcp
- https://docs.carta.com/api-platform/guides/getting-started/introduction/
- https://gateway.idealsvdr.com/api-docs
- https://help.dropbox.com/integrations/connect-docsend-mcp-server
- https://press.spglobal.com/2026-10-22-S-P-Global-Expands-AI-Powered-Capabilities-Across-Private-Markets
- https://securitize.io/apis
- https://www.ansarada.com/data-room/mcp
- https://www.cashflowportal.com/demo/mcp-server
- https://www.chronograph.pe/mcp-connectors/
- https://www.datasite.com/en/resources/ai-at-datasite/datasite-mcp
- https://www.idealsvdr.com/mcp/
- https://www.junipersquare.com/gpx/headless
- https://www.papermark.com/docs/api
- https://www.papermark.com/docs/mcp
- Model Context Protocol: modelcontextprotocol.io
Updated 2026-11-07. Tables regenerate from registry data on every request.