Skip to main content
Glama
pipeworx-io

mcp-seo-keywords

by pipeworx-io

mcp-seo-keywords

SEO Keywords MCP — search volume & difficulty via DataForSEO Labs (dataforseo.com)

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

Tool

Description

seo_keyword_overview

Monthly search volume & difficulty for <keyword> — returns Google search volume, keyword difficulty (0-100), CPC, and competition for up to 10 keywords at once. Keyword research for SEO. Example: seo_keyword_overview({ keywords: ["running shoes", "trail shoes"], location_code: 2840, _apiKey: "your-base64-key" })

Related MCP server: DataForSEO MCP Server

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "seo-keywords": {
      "url": "https://gateway.pipeworx.io/seo-keywords/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/seo-keywords/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1476+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Seo Keywords data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

No MCP client? Call it over HTTP

Our seo-keywords key is reserved for paid accounts, so an anonymous call to POST https://gateway.pipeworx.io/v1/tools/seo_keyword_overview needs your own key passed as _apiKey alongside the arguments. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/seo_keyword_overview. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Related MCP Connectors

  • SEO data for AI agents: Google SERP, keyword research, backlinks, site audits, AI answer visibility.

  • Your agent needs to know what people actually search — volume, ideas, how hard the term is, and whether interest is rising or was a spike last March. **What you can ask for** • "What is the monthly volume and difficulty for these 200 keywords?" • "Give me keyword ideas around this seed, with questions people ask." • "Which keywords does this competitor rank for that we do not?" • "Is interest in this term growing, and where?" • "What does this page already rank for?" **How to use it** Point any MCP client at https://mcp.aisa.one/seo-keywords/mcp and sign in with OAuth — there is no key to create or paste. 49 tools: Google and Bing volume and suggestions, keywords for a site or a URL, clickstream volumes, Google Trends and Ads traffic estimates, plus Semrush difficulty, question keywords, broad match and paid keywords, and Similarweb's keyword and landing page sets. **Why this rather than the source** Three sources for the same number, so a suspicious volume can be checked rather than believed. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Size the demand here, then ask the same agent who ranks for it and who links to them — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/seo/mcp for all of it at once — rankings, keywords, backlinks, site health and AI-answer visibility across DataForSEO, Semrush and Ahrefs.

  • AI-powered SEO and marketing: keyword research, SERP analysis, and content optimization tools.

  • Real SEO data for AI assistants: page audits, Keyword Planner volumes, Search Console history.

Related MCP Servers

  • A
    license
    D
    quality
    D
    maintenance
    Enables LLMs to interact with DataForSEO and other SEO APIs through natural language, allowing for keyword research, SERP analysis, backlink analysis, and local SEO tasks.
    100
    5,611 npm
    82
    MIT
  • A
    license
    C
    quality
    Not graded
    maintenance
    Enables AI assistants to interact with DataForSEO APIs and obtain SEO data including SERP results, keyword research, on-page metrics, backlink analysis, and domain analytics through a standardized interface.
    76
    5,611 npm
    -
  • -
    license
    C
    quality
    Not graded
    maintenance
    Enables AI assistants to access comprehensive SEO data through DataForSEO APIs, including SERP results, keyword research, backlink analysis, on-page metrics, and domain analytics. Supports real-time search engine data from Google, Bing, and Yahoo with customizable filtering and multiple deployment options.
    36
    -
  • F
    license
    Not graded
    quality
    D
    maintenance
    Enables professional SEO/SEM research with geolocalized keyword discovery, competitor analysis, and SERP ranking insights using DataForSEO API.
    -