Ideals vs Firmex: API, MCP and investor access compared

Key differences

• API. Ideals: partner only (REST, API key, for GP users, public docs). Firmex: not documented.
• MCP server. Ideals: available (vendor-maintained). Firmex: not documented.
• Difficulty. The registry rates Ideals 3 of 5 (exports, SFTP or email feeds, no investor-side API) and Firmex 4 of 5 (web login only, exports possible). The rating describes how hard programmatic access is for an investor, not product quality.
• Automation in the terms. Recorded as prohibited for Ideals and tolerated (not addressed in the terms) for Firmex.

What the entries have in common

• Neither entry documents SFTP, webhooks or email notifications.
• Investor-side API: unknown for both, according to the assessment.
• Capabilities: both list Documents.
• Regions: both list Global.
• Known deployments: none documented for either yet.

Which fits which need

Neither product is right for every team. The statements below are conditional and come straight from the registry fields above.

For investors and LP operations teams

• If your investors or your operations team need documents and data through an API, the registry records the API as partner only (aimed at GP users) for Ideals and not documented for Firmex. Access for the investor itself is recorded as unknown for both.
• If you want to reach the data from an AI assistant, the MCP server is available for Ideals and not documented for Firmex. A vendor MCP server can still be limited to the vendor's direct customers, so read the research notes below for who may sign in.
• If you process capital call and distribution notices from your inbox, email notifications are not documented for either.
• If you load files into your own systems, the registry lists no export formats for either.
• If you plan to automate your own login, automation in the terms is prohibited for Ideals and tolerated (not addressed in the terms) for Firmex. Where it is prohibited or unknown, ask the GP or the vendor for a sanctioned channel first.

For GPs, fund administrators and buyers

• If you need to connect the product to your back office, Ideals records API partner only, webhooks not documented and SFTP not documented; Firmex records API not documented, webhooks not documented and SFTP not documented.
• If the product must carry the core LP reporting items (capital calls, distributions, capital account statements and tax documents), the structured capabilities cover none of the four for either.
• If your investors are concentrated in particular markets, the regions recorded are Global for both.
• If you want to see who already runs each product, the registry has no documented deployments for either yet. Operators can add theirs to the registry.
• If your investors will want programmatic access later, the difficulty rating is 3 of 5 for Ideals and 4 of 5 for Firmex, where 1 is a documented self-serve API an investor can use and 5 is web login only with MFA.

For a structured shortlist beyond these two products, see the guide how to choose an investor portal.

What the research says

Ideals Virtual Data Room

Assessment. The API is an enterprise paid add-on for account owners and managers. Admins can enable the vendor MCP per user group within existing permissions, so a GP could in principle enable it for investors; not confirmed. Terms prohibit unapproved tools.

Research notes. High confidence: API is an enterprise paid add-on with per-user keys; vendor MCP connector controlled by room admins per user group; terms prohibit unapproved tools and other means of access. Unknown: whether a GP can enable MCP for investor (guest) groups; SSO, SFTP, webhooks.

• Web: Vendor FAQ says multi-factor authentication is used; methods and SSO not confirmed.
• API: Paid API add-on for enterprise clients ('Request API add-on'). Personal API keys tied to one user, with custom expiry, revocable; corporate account owners and managers with permission can use it. Covers user management, project creation, invitations, bulk document upload and download, reporting, activity logs, archiving. Docs portal content not readable by the researcher.
• MCP: Vendor MCP connector for Claude, ChatGPT and Copilot. Admins enable it in Settings > Integrations for relevant user groups; the AI sees only what the user is authorised to access. Capabilities include folder setup, bidder access, Q&A, search and summarise, activity tracking (implies write). Endpoint, transport, auth and plan not published. Not stated whether guest or bidder groups can be enabled.
• Webhooks: Not mentioned on the API page.
• Terms: Section 3 bars access 'by any means other than through the means provided by Ideals', third-party software that mines or collects information, and any integration or AI tool 'that has not been approved'. Section 12: APIs, integrations and MCP features must be enabled by the account owner or administrator and used within assigned permissions.

Sources: www.idealsvdr.com/api-integrations/ · www.idealsvdr.com/mcp/ · www.idealsvdr.com/terms-of-use/

Firmex Virtual Data Room

Assessment. No API, MCP or integrations found on vendor pages; knowledge base blocked. Web login only as far as known.

Research notes. Little information: the vendor pages fetched mention no API, integrations, SSO, 2FA, MCP or SFTP. Knowledge base blocked (403). Treat as web-only until confirmed.

• Web: SSO and 2FA not mentioned on homepage; support knowledge base returned 403.
• API: No API mentioned on homepage or legal pages.
• Terms: Terms of use bar reverse engineering, unauthorised scans, load tests and penetration tests, and sharing credentials; automated access, bots and scraping are not addressed. Bot-blocking not checked; subscriber agreements not reviewed.

Sources: www.firmex.com/ · www.firmex.com/legal-policies/

Frequently asked questions