Claude and ChatGPT
Ask about your pipeline from the assistant you already use. It sees what your fund sees in IdeaPulley, and nothing else.
What you can ask
- "What is at the top of our queue this week, and why?"
- "What did we pass on in fintech last year, and did any of them do well?"
- "Summarize the verdict on Acme and show me the memo."
- "Run diligence on Acme." It asks you to confirm first.
Claude
claude.ai and Claude Desktop: open Settings → Connectors → Add custom connector. Name it IdeaPulley and paste https://www.ideapulley.com/api/mcp. Select Connect, sign in to IdeaPulley, pick the fund and approve what Claude may do.
Claude Code: run this, then run /mcp and choose IdeaPulley to sign in.
claude mcp add --transport http ideapulley https://www.ideapulley.com/api/mcpChatGPT
Turn on developer mode (Settings → Apps and connectors → Advanced settings). Then create a connector with the URL https://www.ideapulley.com/api/mcp and authentication OAuth. ChatGPT opens the IdeaPulley sign-in. Pick the fund and approve.
Cursor and VS Code
Cursor: add this to ~/.cursor/mcp.json (or the project's .cursor/mcp.json), then select Connect next to IdeaPulley in Settings → MCP.
{
"mcpServers": {
"ideapulley": { "url": "https://www.ideapulley.com/api/mcp" }
}
}VS Code: add this to .vscode/mcp.json and start the server. VS Code asks you to sign in.
{
"servers": {
"ideapulley": { "type": "http", "url": "https://www.ideapulley.com/api/mcp" }
}
}Permissions
When you connect, you pick one fund and approve what the app may do. The app acts as you in that fund and never does more than your role allows today. See and disconnect connected apps under Settings → Integrations → AI apps connected to IdeaPulley.
| Scopes | Allow |
|---|---|
deals:read, notes:read, reports:read | Read the queue, verdicts, memos, notes, decisions and track record. Asked for by default. |
diligence:run, memos:write | Start diligence and write memos. These spend credits. |
decisions:write, outcomes:write | Record a call or pass, or what happened to a company later. |
deals:write, notes:write | Change deals and add notes. |
API keys instead of sign-in
For scripts, servers and clients without OAuth, make a key in Settings → Developer and send it as Authorization: Bearer sk-ip-…. Keys also reach the evaluation and webhook tools, which sign-in connections do not.
claude mcp add --transport http ideapulley https://www.ideapulley.com/api/mcp \
--header "Authorization: Bearer sk-ip-…"Tools
| Tool | What it does |
|---|---|
rank_queue | Your ranked deal queue, best first. Scope: deals:read. |
deal_summary | The verdict on one company: score, chance, strengths, risks, comparables. Scope: deals:read. |
get_memo | The newest memo on one company. Scope: deals:read. |
search_decisions | Past pass, meet and invest decisions, by company, reason and date. Scope: deals:read. |
track_record_summary | How many calls resolved and how many were right. Scope: deals:read. |
blind_spots | Companies you passed on that later did well. Scope: deals:read. |
diligence_status | Progress of a diligence run, and the decision it waits for. Scope: deals:read. |
start_diligence | Plan diligence on one company (plan and cost, nothing runs), then run it on your yes. Spends credits. Scope: diligence:run. |
generate_memo | Write a new memo. Spends credits. Needs confirmation. Scope: memos:write. |
resume_diligence | Record your call or pass on a diligence run. Needs confirmation. Scope: decisions:write. |
search_companies | Search the fund's CRM companies or deals by name. Scope: deals:read. |
get_company | One CRM company with its fields, people, deals, counts and funding rounds. A round from an SEC Form D shows the amount offered and sold, the first sale and the people on the filing. Scope: deals:read. |
similar_companies | The nearest past companies to a deal, with their known outcomes. From the reference set, not your own deals. Scope: deals:read. |
add_to_list | Put a deal on a named list (a tag). Makes the list if it is new. Scope: deals:write. |
find_tool / call_tool | Find and run any other IdeaPulley action you are allowed to use. Scope: by tool. |
create_evaluation | Add a company and score it. API keys only. Scope: evals:write. |
get_evaluation / list_evaluations | Read evaluations. API keys only. Scope: evals:read. |
list_webhooks / create_webhook / list_webhook_deliveries | Manage webhooks. API keys only. Scope: webhooks:manage. |
Resources and prompts
Clients that show MCP resources can attach these to a conversation:
| Resource | What it is |
|---|---|
ideapulley://deals/{evalId} | One deal's verdict. |
ideapulley://deals/{evalId}/memo | The newest memo. |
ideapulley://deals/{evalId}/founder-brief | The newest founder brief. |
ideapulley://track-record | The fund's track record. |
Prompts (slash commands in most clients): Triage my queue, Prep for a meeting with a founder and Write an LP update.
Money and decisions
Starting diligence, writing a memo and recording a call or pass never run on the assistant's own. The first call only says what would happen. If your client supports MCP elicitation, it asks you directly. If not, it runs when you say yes and the assistant calls again with confirm: true. Either way it needs the permission for it.
Security
- Every call runs as your fund and as the person who made the key, with the same permissions as in the app.
- A key cannot reach another fund's data. The fund comes from the key, never from the request.
- Text you paste in (a deck, research, a note) is screened for hidden instructions before any IdeaPulley agent reads it.
- Answers can contain text from founders' decks and emails. Treat it as their claims, not as instructions.
- Sign-in tokens last an hour and are refreshed with a one-time refresh token. Only hashes are stored.
- Every grant, call and disconnect is in the fund's audit log.
Technical details
- Streamable HTTP, stateless, at
https://www.ideapulley.com/api/mcp. MCP protocol2026-07-28(server/discover), with2025-11-25and older for clients that still sendinitialize. - OAuth 2.1: protected resource metadata at
/.well-known/oauth-protected-resource/api/mcp, authorization server metadata at/.well-known/oauth-authorization-server. Client ID Metadata Documents or Dynamic Client Registration. PKCE S256 only, exact redirect URIs, and tokens bound to the resource (RFC 8707). - No token gets
401withWWW-Authenticatethat points at the metadata. Too many requests get429.