DataLeadsPRO DataLeads Keyword Research MCP

An MCP server that provides keyword ideas and question discovery for any seed term, including search volumes, difficulty scores, and SERP intent. It leverages the DataLeads API suite with built-in anti-bot handling and protected-page support, allowing agents to perform SEO research without managing proxies or infrastructure.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Community listingStreamable HTTPNo sign-inEndpoint checked 2026-11-06Published by DataLeadsPRO

You need:Replace YOUR_CLIENT_KEY with your key.

MCP endpoint (Streamable HTTP)

https://data.dataleads.pro/mcp/keyword-research

Vendor documentation

What its tools do

2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

2 of 2 have a description · 0 of 2 declare behavior hints · 0 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 6, 2026, 3:10 PM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Discover keyword ideas for a specific seed term
Find related questions for content creation
Analyze search volume and difficulty metrics
Retrieve SERP intent data for SEO strategy

Source and maintenance

Community listingRegistry 1.0.1

mcp-registry: io.github.DataLeadsPRO/keyword-research@1.0.1 Source repository

Maintenance checked: Nov 6, 2026, 2:37 PM UTC

Protocol and capabilities

Server: Keyword Research API 1.30.0
MCP protocol negotiated in check: 2025-11-25
Tools: 2 advertised
Resources: 0 advertised
Resource templates: 0 advertised
Prompts: 0 advertised

Server-advertised capabilities

{
  "tools": {
    "listChanged": false
  },
  "prompts": {
    "listChanged": false
  },
  "resources": {
    "subscribe": false,
    "listChanged": false
  },
  "experimental": {}
}

Tools

2 advertised

keywords_ideas

Advertised by the server during the last successful anonymous check.

V1 Keywords Ideas

keywords_ideas input schema

{
  "type": "object",
  "title": "keywords_ideasArguments",
  "properties": {
    "query": {
      "type": "string",
      "title": "Query",
      "default": null
    },
    "country": {
      "type": "string",
      "title": "Country",
      "default": null
    },
    "language": {
      "type": "string",
      "title": "Language",
      "default": null
    },
    "expansion": {
      "type": "boolean",
      "title": "Expansion",
      "default": null
    },
    "maxTimeout": {
      "type": "integer",
      "title": "Maxtimeout",
      "default": null
    }
  }
}

keywords_questions

Advertised by the server during the last successful anonymous check.

V1 Keywords Questions

keywords_questions input schema

{
  "type": "object",
  "title": "keywords_questionsArguments",
  "properties": {
    "query": {
      "type": "string",
      "title": "Query",
      "default": null
    },
    "country": {
      "type": "string",
      "title": "Country",
      "default": null
    },
    "language": {
      "type": "string",
      "title": "Language",
      "default": null
    },
    "maxTimeout": {
      "type": "integer",
      "title": "Maxtimeout",
      "default": null
    }
  }
}

Prompts

0 advertised

No prompt definitions available.

Resources

0 advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

2026-11-06: 1 of 1 checks answered
2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 1759 ms
95th percentile latency: 1759 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 6, 2026, 3:10 PM UTC · probe · passed · 1759 ms · metadata changed · 2 tool(s), 0 resource(s), 0 resource template(s), 0 prompt(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http dataleads-keyword-research-mcp https://data.dataleads.pro/mcp/keyword-research

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add dataleads-keyword-research-mcp --url https://data.dataleads.pro/mcp/keyword-research

Cursor

Merge this server into .cursor/mcp.json in your project, then enable dataleads-keyword-research-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "dataleads-keyword-research-mcp": {
      "url": "https://data.dataleads.pro/mcp/keyword-research"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "dataleads-keyword-research-mcp": {
      "type": "streamableHttp",
      "url": "https://data.dataleads.pro/mcp/keyword-research",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start dataleads-keyword-research-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "dataleads-keyword-research-mcp": {
      "type": "http",
      "url": "https://data.dataleads.pro/mcp/keyword-research"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http dataleads-keyword-research-mcp https://data.dataleads.pro/mcp/keyword-research

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://data.dataleads.pro/mcp/keyword-research

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "dataleads-keyword-research-mcp": {
      "serverUrl": "https://data.dataleads.pro/mcp/keyword-research"
    }
  }
}

Let your agent find its tools

Find servers like DataLeadsPRO DataLeads Keyword Research MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

See all 8,318