> For the complete documentation index, see [llms.txt](https://docs.coresignal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coresignal.com/integrations/coresignal-mcp/cursor.md).

# Connect Coresignal MCP to Cursor

Connect Coresignal MCP to Cursor CLI to search, enrich, and export data.

### What is Cursor?

Cursor CLI brings the agent from the Cursor editor to the command line. In the terminal, it reads and edits code, runs commands, and connects to external tools and data through MCP servers.

After you add Coresignal MCP, Cursor CLI can search, enrich, and export Coresignal data for developers, data engineers, and technical GTM teams, who can then use the results directly in their scripts, pipelines, and applications.

### How to connect Coresignal to Cursor?

{% stepper %}
{% step %}
Register and create an account with [Coresignal](https://dashboard.coresignal.com/sign-up).
{% endstep %}

{% step %}
In Cursor, open **Settings** → **Tools & MCPs** → **Add Custom MCP** and paste:

{% code lineNumbers="true" expandable="true" %}

```
{
 "mcpServers": {
  "coresignal": {
   "url": "https://mcp.coresignal.com/mcp/v2"
  }
 }
}
```

{% endcode %}
{% endstep %}
{% endstepper %}

### FAQ

<details>

<summary>How do I sign in to Coresignal MCP in Cursor?</summary>

After adding the server in **Settings → Tools & MCPs**, select the option to connect or log in next to Coresignal. Your browser opens the Coresignal dashboard, where you sign in and approve access.

</details>

<details>

<summary>What can I ask Cursor to do with Coresignal data?</summary>

You can search, enrich, and export company, employee, and job data, then use the results in your scripts, pipelines, and applications. Available tools cover natural-language search, field discovery, full profile pulls, contact enrichment, and reading delivered files.

</details>

<details>

<summary>What are the most common Coresignal MCP setup issues in Cursor?</summary>

Common issues setting up Coresignal MCP in Cursor are:

* invalid JSON in the custom MCP configuration
* the old endpoint without `/v2`
* skipping the Coresignal sign-in
* a Coresignal account without available credits

</details>

<details>

<summary>How do I remove Coresignal MCP from Cursor or turn it off?</summary>

To turn it off, toggle coresignal off in **Settings → Tools & MCPs**. To remove it, delete the coresignal entry from your `mcp.json`, either global (`~/.cursor/mcp.json`) or project-level (`.cursor/mcp.json`).

</details>

<details>

<summary>How many credits does Coresignal MCP use in Cursor?</summary>

The credit cost depends on the task. Field discovery and reading delivered files are free. Full profile pulls cost 1–20 credits per record. See our [pricing](https://docs.coresignal.com/pricing/).

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coresignal.com/integrations/coresignal-mcp/cursor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
