# AngelList MCP connector

The AngelList connector brings firms, vehicles, capital accounts, distributions and financial statements into Claude, ChatGPT, Cursor and the Elaichi Agent, read-only, so each person can ask about fund data inside their own AngelList access.

Source: https://elaichi.ai/connectors/angellist/

## Facts

| | |
| --- | --- |
| Application | AngelList |
| Category | Accounting |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. AngelList builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | help.angellist.com/hc/en-us |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once AngelList is connected

- Which distributions did Fund II pay out this quarter?
- Summarize the latest financial statements for our growth vehicle
- What is Acme Capital's current capital account balance?

## Connect AngelList in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick AngelList.
2. Optionally set Share with, then press Connect.
3. Approve it in AngelList. AngelList's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which AngelList tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## AngelList MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## AngelList MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## AngelList MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect AngelList to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a AngelList tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with AngelList through Elaichi

### Check a capital account before the call

Finance. Pull up a limited partner's capital account, with contributions and distributions to date across every vehicle, before you pick up the phone.

### Answer an LP question without a spreadsheet

Investor relations. Ask which distributions went out from a vehicle this quarter and what each one was for, then reply in the same window.

### Pull the latest statements for a vehicle

Fund operations. Ask for the most recent financial statements and supporting documents for a vehicle and have them summarized in plain language.

### Reconcile quarter-end distributions against the books

Accounting. List every distribution a vehicle paid in the period, with amounts and dates, and compare it with what the ledger shows.

### See every asset across the firm's vehicles

Leadership. Ask which assets each vehicle holds and how they are spread across the firm, without clicking through each vehicle in AngelList.

### Find the document behind a number

Compliance. Ask for the statement or document that supports a capital account figure and get it named, so you can check it yourself.

## Elaichi vs Zapier MCP vs Composio for AngelList

All three can connect AngelList to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over AngelList tools | Allow or restrict single AngelList tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per AngelList call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect AngelList to Claude?

Connect AngelList in Elaichi first: you sign in to AngelList with your own account and approve access, and there is no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude then signs you in to Elaichi and AngelList is ready to ask about.

### Does AngelList work with ChatGPT and Cursor as well as Claude?

Yes. Once AngelList is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect AngelList once and every client picks it up.

### What can an AI agent actually do with my AngelList data?

It can read what you can see in AngelList: firms, vehicles, capital accounts, assets, distributions, financial statements and documents. You can ask which distributions a vehicle paid this quarter, what a limited partner's capital account shows, or for a summary of the latest statements. The AngelList connector is read-only, so nothing in AngelList is changed. Short, specific asks tend to work better than long sentences.

### Does connecting AngelList give the AI access to every fund and vehicle?

No. Access follows the person who signed in, so the AI sees only the firms, vehicles and capital accounts that person can already open in AngelList. Elaichi can narrow that further for a team or a role, and it never widens it.

### Can my team share one AngelList connection?

Yes. One person connects AngelList in Elaichi and shares it with a team, and nobody else handles a password or credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who looked at a capital account or a statement.

### Can I stop an agent from deleting or changing things in AngelList?

The AngelList connector is read-only, so an agent cannot change, delete or create anything in AngelList to begin with. On top of that, Elaichi restrictions work per action, and a restricted action is never advertised to Claude, ChatGPT or any other client, so no prompt can reach it.

### What happens to an AngelList connection when someone leaves?

Offboarding that person in Elaichi ends their AngelList access at once, in every client. If they had shared an AngelList connection with a team, it keeps working for everyone else. Disconnecting AngelList once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

### Does the AngelList MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. AngelList is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for AngelList?

Yes. Both let Claude, ChatGPT or Cursor use AngelList. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every AngelList call.

### How is Elaichi different from Composio for AngelList?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to AngelList: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.