Affinity
Search your CRM, prep for meetings and update deal records from your AI assistant.
Query capital accounts, capital calls, distributions, statements and fund documents from an AI assistant.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The AngelList MCP server connects venture fund administration records to Claude, ChatGPT and any MCP client. Sold as AngelList Link, it answers questions about capital calls, LP commitments, distributions and fund documents against the ledger a fund already runs on. Its directory record carries a rare full-paragraph read-only disclosure, and this one survives every check.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
download_document puts a file is undocumented. Marketing describes download links, which implies a URL, but no signing, expiry or session requirement is published, and no response schema exists. Ask AngelList through the Trust Portal if this matters to your diligence.inputSchema, readOnlyHint or destructiveHint was readable for any of the 28 tools. The read-only finding rests on scope metadata and vendor statements, not annotations.documentation field points at https://help.angellist.com/, which carries no MCP content; the real articles are reachable only by searching the help centre.Yes, today. Four independent checks agree: the directory paragraph, AngelList's security page, the product FAQ, and the OAuth descriptor whose sixteen scopes all end in :read. But AngelList states plainly that write access is coming next, with the assistant preparing an action for a human to approve. The claim is verified for this build, not permanently.
General partners and their teams only. AngelList answers this directly in its product FAQ, stating the product is not for LPs and that limited partners continue receiving statements and documents as they do now. Your fund must also be administered on AngelList — the connector queries the records AngelList itself holds, not an external fund administrator's system.
It retrieves a fund document, and AngelList's marketing describes results grouped by vehicle with download links. That wording points to a URL rather than an inline file, but AngelList publishes no tool reference, so the return shape is not documented. Whether the link is signed, how long it lives, and whether it requires a session are all unstated.
Yes, within your existing entitlements. AngelList states the connector reaches investor and LP records you administer, and eleven of the twenty-eight tools address partner-level data — capital accounts, subscriptions, distributions and partner lists. Those individuals are third parties who never agreed to an AI connector. The connector adds no new access; it adds a new destination for data you could already see.
Sixteen named scopes, and every single one ends in :read. The RFC 9728 descriptor lists them with human-readable descriptions covering vehicles, capital accounts, capital calls, distributions, documents, financial statements and more. No write scope is advertised anywhere. This is the strongest wire-level corroboration of a read-only claim this catalogue has recorded.
No — it documents none by name. AngelList's two published MCP articles describe data categories such as firms, vehicles, capital accounts and documents, but never name an individual tool. The twenty-eight names on this page come from Anthropic's directory snapshot alone. That inverts the usual gap: the listing is the only tool-level source that exists.
help_center article search JSON API, which returns clean article text; article updated_at 2026-07-28. Source of the setup instructions per client, the data-category list, the mcp-remote fallback, the OAuth 2.1 with dynamic client registration statement, and the six example prompt workflows used for the vocabulary decoder and use cases) · retrieved 2026-08-19updated_at 2026-07-23. Source of the read-only can/cannot lists, the same-infrastructure entitlement statement, "investor and LP records you administer", SOC 2 Type II, TLS in transit, and the guidance naming the AI client's own data handling as the biggest exposure) · retrieved 2026-08-19:read scopes with a scope_descriptions gloss for each, authorization_servers naming https://auth.angellist.com, EdDSA under resource_signing_alg_values_supported. The path-append form at /.well-known/oauth-protected-resource/mcp returns a byte-identical body with a matching weak etag; the path-insert form at /mcp/.well-known/oauth-protected-resource returns 404 with a text/plain body) · retrieved 2026-08-19S256, registration_endpoint for dynamic client registration, two grant types, and scopes_supported of openid, email, profile only. Both .well-known forms on the MCP host return 404) · retrieved 2026-08-19initialize probe of https://mcp.angellist.com/mcp (2026-08-19; HTTP 401 with a JSON token_missing error body and a www-authenticate challenge naming the root-form resource_metadata URL. No authentication was attempted and no tool was called) · retrieved 2026-08-19tool_names, the empty prompt_names array, the permissions paragraph, the partner tier, the categories and the documentation root URL. The 1,434-of-1,897 permissions count was computed from this snapshot on 2026-08-19) · retrieved 2026-08-16Connect AngelList once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.