# Datacircle MCP server

> Compare benchmarked GTM API providers and plans by price, score, rate limits, speed and returned fields.

- Listing: https://mcp.tc/i/datacircle
- Connect: use the server's own URL `https://api.datacircle.dev/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Search & Web Data](https://mcp.tc/c/search-web)
- Vendor: Datacircle
- Homepage: <https://datacircle.dev>

## About

Datacircle benchmarks go-to-market data APIs such as LinkedIn, email, phone, SEO and social profile providers. The server exposes its sheet of APIs and plans, so an assistant can list the APIs, search plans by API, provider or name, and sort by price or score. Each plan includes price per 1,000 results, a score out of 100, rate limits, speed, returned fields and a link to its page on datacircle.dev.

It runs as a hosted streamable HTTP endpoint at https://api.datacircle.dev/mcp. Both tools are read-only. No sign-in or API key is needed.

## What it can do

- List all GTM APIs on the sheet with plan and provider counts
- Search plans by API, provider or plan name
- Sort plans by price or benchmark score
- See rate limits, speed and returned fields per plan
- Get links to provider rankings and plan pages on datacircle.dev

## Tools (2)

- `list_apis`: Lists every API on the sheet with its plan count, provider count, sheet page and best page. (read-only)
- `search_plans`: Searches API plans by API, query and sort, with limit and offset; returns price, score, limits and… (read-only)

## Example prompts

- "Which email finder API is cheapest per 1,000 results on Datacircle?"
- "List the APIs Datacircle benchmarks."
- "Show the top-scoring LinkedIn profile API plans."
- "Compare phone validation API plans by price and rate limits."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http datacircle https://api.datacircle.dev/mcp
```

2. Start Claude Code and type `/mcp`. **datacircle** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Datacircle** and paste this URL:

```url
https://api.datacircle.dev/mcp
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Datacircle&connectorUrl=https%3A%2F%2Fapi.datacircle.dev%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://api.datacircle.dev/mcp` and click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://api.datacircle.dev/mcp` as the server URL, then for authentication choose **No authentication**.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=datacircle&config=eyJ1cmwiOiJodHRwczovL2FwaS5kYXRhY2lyY2xlLmRldi9tY3AifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "datacircle": {
      "url": "https://api.datacircle.dev/mcp"
    }
  }
}
```

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=datacircle&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fapi.datacircle.dev%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"datacircle","type":"http","url":"https://api.datacircle.dev/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "datacircle": {
      "type": "http",
      "url": "https://api.datacircle.dev/mcp"
    }
  }
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "datacircle": {
      "serverUrl": "https://api.datacircle.dev/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add datacircle --url https://api.datacircle.dev/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.datacircle]
url = "https://api.datacircle.dev/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http datacircle https://api.datacircle.dev/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "datacircle": {
      "type": "http",
      "url": "https://api.datacircle.dev/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://api.datacircle.dev/mcp`.

## Recent changes

- 2026-11-17 02:51 UTC: 1 tool changed. Source: automatic check. Changed: search\_plans.
- 2026-11-16 20:49 UTC: 1 tool changed. Source: automatic check. Changed: search\_plans.
- 2026-11-16 11:57 UTC: 1 tool changed. Source: automatic check. Changed: search\_plans.
- 2026-11-15 20:56 UTC: Server instructions changed. Source: automatic check. Worth a look: new server instructions.
- 2026-11-15 17:57 UTC: 1 tool changed. Source: automatic check. Changed: search\_plans.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/datacircle#history (Atom feed: https://mcp.tc/i/datacircle/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 2.0.0
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-18 (reachable)
- Listed: 2026-11-06
- Updated: 2026-11-14

---
Source: https://mcp.tc/i/datacircle (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
