Skip to main content
Metal MCP connects AI assistants directly to your Metal workspace. Ask Claude, ChatGPT, or Cursor to find investors, map warm intros, update your pipeline, or prepare you for a call, and it happens in Metal without you opening the app. It is built on MCP (Model Context Protocol), the open standard for connecting AI models to software. Any MCP-compatible client works, and teams building custom agents or internal tooling can build on the same connection.

Same Intelligence, New Surface

MCP is an access layer, not a separate product. Everything it does runs on the same proprietary data, relevance scoring, and network intelligence that powers the Metal app, so results stay consistent wherever you work.

​
Common Use Cases

Search the market by stage, sector, geography, thesis, or recent activity. Pull full investor profiles, check sizes, portfolio patterns, and co-investor relationships. Your assistant can research companies, their funding history, and founders, or find the investors behind any founder and the deals a specific partner has personally led.
“Find seed-stage fintech investors in Europe who have led a round in the last 12 months, and show me their typical check size.”

​
Getting Connected

Metal is listed on Claude’s connector directory, so there is nothing to configure.
1

Find Metal in the directory

In Claude, open Settings → Connectors, search for Metal Fundraising, and click Connect.
2

Sign in and choose your organization

Authenticate with your Metal account through a standard OAuth flow and select the organization you want to connect. Access is scoped to that organization.
3

Approve permissions

Read and write permissions are granted separately. Start read-only if you prefer, and enable write access when you are ready for your assistant to update your pipeline, tags, and notes.

​
Other AI clients

For ChatGPT, Cursor, or any MCP-compatible client, add Metal as a custom connector.
1

Sign in to Metal

Make sure you are signed in to Metal in your browser at app.metal.so.
2

Add a custom connector

In your AI client, go to connector settings and choose to add a custom (manual) connector. Name it:
3

Enter the server URL

The URL begins with api.metal.so, not app.metal.so. Copy it rather than typing it — this is the most common setup mistake.
4

Authenticate

Approve the sign-in prompt, select your organization, and grant the permissions you want. You’re ready to go.
Setup takes about two minutes. Access can be revoked at any time from your client’s connector settings.

​
Access and Security

Scoped to You

Your assistant sees only what your Metal account can see, within the organization you selected at connection time.

Granular Permissions

Read and write access are separate scopes, so you control exactly what your assistant is allowed to change.
Your fundraising configuration (stage, sector, geography, existing investors) is managed in the Metal app and is not editable through MCP. This keeps the setup that drives your recommendations deliberate and in one place.

​
Troubleshooting

“Authorization with Metal failed.” This is usually a stale or half-finished earlier connection attempt. Remove the Metal connector from your client entirely, then reconnect from scratch following the steps above. The connector won’t authenticate. Double-check the server URL is https://api.metal.so/mcp. Entering app.metal.so instead of api.metal.so is the most common cause of failed connections. Still stuck? Email support@metal.so and include the reference code from the error message (it starts with “ofid_”) — it lets us find your connection attempt immediately.
For questions, or if there is an ambitious workflow you want to build on Metal MCP, reach out to us (support@metal.so).