Coresignal MCP

What Coresignal MCP MCP server does

Coresignal MCP MCP server exposes Coresignal’s B2B data through the Model Context Protocol. The service covers employee, company, and job records, with the source describing datasets of more than 895 million employees, 70 million companies, and 468 million job postings.

Agents can search these entities in natural language, inspect available field names, retrieve complete or selected records, obtain verified business emails for employee IDs, and read rows from server-side result files. Search responses include match evidence so an agent can see which fields caused a record to match.

How it works

The hosted endpoint is https://mcp.coresignal.com/mcp/v2. A client connects over HTTP or streamable HTTP and starts an OAuth 2.1 login in the browser. After authentication, the service resolves the team API key associated with the Coresignal account; the key is not entered into the client configuration.

entity_search accepts an employee, company, or job type and a plain-language query. It charges 20 credits per search, returns an exact count and up to 20 preview rows, and provides a one-hour search handle. Passing that handle to entity_fetch avoids running and paying for the search again. entity_fields can locate field names by keyword at no credit cost, which helps construct a projected fetch.

Large responses can be delivered as files rather than inserted into the conversation. The server returns a signed HTTPS link that expires after one hour. When a client cannot download the file, artifact_read can page through it in the MCP session without consuming Coresignal credits.

Setup and configuration

A Coresignal account with an active credit subscription is required. The README also states that a team API key must be provisioned in the dashboard, although the MCP login resolves it automatically. The first connection opens a browser for dashboard authentication, and no environment variables or secrets are needed in the client configuration.

Add the remote URL using the client’s MCP configuration or its server-add command. The documented clients include Claude Desktop, Claude Code, Codex, Cursor, Visual Studio Code, and Cline. Claude Desktop may require mcp.coresignal.com in its domain allowlist for direct file downloads; artifact_read remains an alternative for reading files in-chat.

Tools and capabilities

• entity_search: Searches employees, companies, or jobs using natural language.
• entity_fields: Finds entity field names by keyword for free.
• entity_fetch: Retrieves full JSONL records or selected fields by search handle or ID.
• email_enrich: Returns verified business emails for employee IDs in CSV format. Found emails cost 10 credits each; misses are free.
• artifact_read: Reads delivered-file rows in pages without Coresignal credit charges.

Searches cost 20 credits each. Fetches cost 20 credits per employee or company record and one credit per job record. Responses expose credits_consumed, and the service can request confirmation for expensive operations.

Limitations and notes

The Coresignal MCP MCP server requires a Coresignal account with available credits. artifact_read avoids additional Coresignal charges but still adds returned data to the model conversation, so paging through a large file can consume context and input tokens. Downloading the file is preferable when the client and its security settings permit it.

Search handles last one hour, and signed artifact URLs also expire after one hour. The README does not describe a local installation package; the documented deployment is the hosted remote endpoint. Coresignal MCP MCP server access therefore depends on the remote service, browser authentication, and the account’s subscription or trial credits.