Skip to main content
The Metal MCP server lets MCP-compatible AI tools like Cursor, Claude, and ChatGPT securely access your firm’s Metal data. Once connected, your assistant can search companies, deals, people, and documents, and run workflows, grounded in your organization’s knowledge. Model Context Protocol (MCP) is an open standard for connecting AI applications to external tools and data.

​
Server URL

Connect your AI tool to the hosted Metal MCP server:
The server speaks streamable HTTP and authenticates with OAuth, so there’s no API key to manage. When you connect, your tool opens a browser window to sign in with your Metal account. If you belong to more than one organization, you choose which one to connect.
Access is scoped to your Metal user and organization, and respects the same permissions you have in the app.

​
Prerequisites

1

Ask an admin to enable MCP

An organization admin must turn on the MCP server first: in the Metal app, go to Settings → Organization → API & MCP Access and enable Allow access to the Metal MCP server.
2

Use an MCP-compatible tool

You need a client that supports remote MCP servers, such as Cursor, Claude, or ChatGPT. See other clients for everything else.

​
Connect your tool

Cursor

Add Metal as a remote MCP server in Cursor.

Claude

Add Metal as a connector in Claude.

ChatGPT

Add Metal as a connector in ChatGPT.
Using a different client? See other MCP clients.

​
Portability and interoperability

Metal exposes your firm’s context through standards-based interfaces, so your data is not locked into one chat surface or one model provider.
  • Open agent protocol: MCP is an open standard. Any MCP-compatible tool can connect to https://mcp.metal.ai/mcp, including tools such as Cursor, Claude, ChatGPT, and clients that bridge local-only MCP support with mcp-remote.
  • Programmatic API access: the Metal REST API returns JSON for the same core records your team works with in the app, including companies, deals, people, documents, activities, lists, enrichments, scores, financial metrics, workflows, and data observations. Use the API to sync records in, read enriched context out, and feed downstream systems. See the API reference.
  • Customer-controlled identifiers: companies, deals, and people can carry your own externalId and externalReference values, which makes it easier to reconcile Metal records with your CRM, data warehouse, or other systems. See the data model.
  • Permission-aware access: MCP uses OAuth and API requests use organization-scoped API keys, so connected tools only see data they are allowed to access.

​
Available tools

Once connected, your AI client discovers 44 tools for searching and reading your firm’s data, running workflows, and (with the right permissions) authoring workflows. Tools return JSON in a text content block — see the tools reference for parameters, response shapes, and examples. The server also exposes resources (field definitions, document types) and prompts (guided research workflows). Details are in the tools reference.
The exact tools available to you depend on your OAuth scopes, organization settings, and app permissions.

​
Troubleshooting

Confirm an admin has enabled Allow access to the Metal MCP server under Settings → Organization → API & MCP Access. Then clear your tool’s saved Metal connection and reconnect so it can complete a fresh OAuth sign-in.
Disconnect and reconnect. During sign-in, Metal prompts you to choose an organization when your account belongs to more than one.
Use a bridge like mcp-remote. See other MCP clients.

Related topics

External MCP serversOther MCP clientsMCP tools referenceConnect CursorConnect ChatGPT