Coresignal MCP
Coresignal MCP v2 is a server that connects Coresignal's data directly to LLM-powered applications, including Claude, Cursor, and others. It gives AI assistants access to Coresignal's multi-source company, employee, and job data from within the chat interface. The server handles query construction, authentication, credit accounting, and result delivery, enabling an agent to work with large-scale data without manually building API calls.
Find available information on GitHub.
Features
Data field discovery
Get data you need by searching for the right data fields. Discovery uses semantic search to find all matching top-level and nested data fields related to the keywords used in the prompt. This is useful for exploring what data is available for a given entity. Data field discovery requests incur no credit cost, allowing unlimited use during query formulation.
Credit reporting and consent before spend
Each response shows the exact credits used for the request, providing detailed per-call spending information.
Small, inexpensive data previews continue seamlessly, but requests with potentially high costs require a check-in first. Before performing a large or expensive data retrieval, the server pauses to verify the scope, including the record count and estimated credit cost.
Automatic file delivery
Inline delivery is the primary mode of interaction: results are returned as a preview, which indicates whether your prompt is efficient. A file is created instead when you request the complete available record data. The response includes a link to the file, keeping large pulls, such as thousands of records, from overwhelming the conversation, while the complete data remains available for further processing. Remember that enabling downloads from third-party tools isn't universal: review each tool's documentation to set up the required permissions (e.g. Claude desktop).
Endpoint
Use the following endpoint to connect to the Coresignal MCP server:
Endpoint
https://mcp.coresignal.com/mcp/v2
Transport
Streamable HTTP
Authentication
OAuth 2.1 sign-in via the Coresignal dashboard
Local install required
No
API key required
No. The server fetches your team's key live on request
Prerequisites
Before you begin, ensure you have:
A Coresignal account. If you don't have one yet, you can register in Coresignal dashboard.
Available credits for search, record pull, and email enrichment actions.
An MCP-compatible client that supports remote servers over Streamable HTTP.
A browser for the one-time sign-in flow.
Connect Coresignal MCP
Choose the option to add a custom or remote server and use https://mcp.coresignal.com/mcp/v2 to connect to Coresignal MCP. Several MCP-compatible clients integrations steps are listed below.
Claude Code
Run this in your terminal:
Then verify the connection:
Codex
Run this in your terminal:
Then verify the connection:
AntigravityCLI
Edit ~/.gemini/config/mcp_config.json file
OpenCode
Run this in your terminal:
Then verify the connection:
Cursor
Open Settings → Tools & MCPs → Add Custom MCP and paste:
Available tools and cost
All requests use the same Coresignal credit balance as other activities in your account. Costs are fixed per action and are included in each response.
entity_search
Natural-language search
Describe the data you want in natural language. The server builds a query, explains the search, and returns results with an exact-match count and a preview.
20 credits per search
entity_fields
Data field discovery
Semantic search across top-level and nested fields, for scoping a query or exploring what's available on an entity.
Free
entity_fetch
Full profile pull
Retrieve a complete company, employee, or job record.
1-20 credits per record. See Pricing
email_enrich
Email enrichment
Get a publicly accessible, strictly business-related work email for an employee. The system's public email lookups automatically exclude employees in the EEA and UK to comply with GDPR. Blocked lookups are not charged.
10 credits per email
Limitations
Coresignal MCP has several limitations:
Business-related email enrichment cannot be provided for employees in the European Economic Area (EEA) and the United Kingdom (UK) due to privacy regulations.
Tool availability may vary by MCP client and rollout status.
Sample queries and flows
See illustrative sample flows that can help you craft your own requests effectively.
Legacy Coresignal MCP
Legacy Coresignal MCP is a server that connects Coresignal's latest Multi-source Company API, Multi-source Employee API, and Base Jobs API information directly within chat interface.
Prerequisites
To connect to the remote Legacy Coresignal MCP server using mcp-remote you need to have Node.js installed.
Credits for requests performed through the MCP server will also be deducted from the same credit balance.
Integration with AI assistants
Learn integration steps for a few AI assistant tools.
Enter your API Key as the <api_key> value. Get your key from Coresignal's self-service platform.
Do not forget to refresh the tool after the integration steps.
Claude Desktop
To set up your Claude Desktop assistant, add this entry to your claude_desktop_config.json file:
Cursor
Cursor has integrated support for MCP servers:
Go to: Cursor > Settings > Cursor Settings > MCP
Click on the
Add new global MCP serverbuttonAdd the following configuration:
Available tools
The Legacy Coresignal MCP server gives access to several API data entities:
coresignal_company_multisource_api – data from Multi-source Company API
coresignal_employee_multisource_api – data from Multi-source Employee API
coresignal_job_api – data from Base Job API
Last updated
Was this helpful?