# seodata.dev: keyword search volume [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/seodata-dev/mcp-server  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/seodata-dev-keyword-search-volume

## Description
Keyword search volume, CPC, competition and similar keywords for 50+ countries.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "seodata-dev-keyword-search-volume": {
    "url": "https://mcp.seodata.dev/mcp"
  }
}
```

## Documentation

## What seodata.dev: keyword search volume MCP server does

seodata.dev: keyword search volume provides keyword research data to MCP-compatible AI assistants. The hosted service covers more than 50 countries and returns monthly Google search volume, CPC in US dollars, competition scores from 0 to 1, and related keywords with their own volumes and CPC values.

The service is read-only. It does not modify websites, campaigns, documents, or other external systems. The repository contains connection configurations and registry metadata; the MCP server itself runs on seodata.dev.

## How it works

Clients connect to `https://mcp.seodata.dev/mcp` using the Streamable HTTP transport. Authentication is optional. A client can use OAuth 2.1 with PKCE and dynamic client registration, or send an API key as a Bearer token. Anonymous requests are supported within the no-account allowance.

Each keyword lookup is counted separately for one keyword in one country. The country input uses an ISO 3166-1 alpha-2 code, with `us` as the default for single-keyword requests. The service shares quotas and API keys with the seodata.dev HTTP API.

## Setup and configuration

There is no local package or process to install. Add the remote MCP URL to a compatible client and let that client handle OAuth, or provide the API key in the `Authorization` header. Clients that accept only a URL can use the key query parameter form, but the resulting URL should be kept private.

The README documents connection methods for Claude Desktop and Claude Code, Cursor, VS Code, Codex, and Gemini CLI. Claude Code can be configured with its HTTP transport command, while the other documented clients use their respective MCP configuration or extension flow.

## Tools and capabilities

The server exposes three read-only tools:

- `lookup_keyword` accepts one keyword and a country. It returns volume, CPC, competition, and similar keywords.
- `lookup_keywords` accepts between one and 25 keywords plus a country, making it suitable for comparing or prioritizing a list.
- `get_usage` reports the plan associated with the connection and the number of lookups remaining today and this month.

For example, an agent can use `lookup_keyword` to inspect a single term, then review related terms returned by the same request. It can use `lookup_keywords` when the candidate list is already known.

## Limitations and notes

The no-account tier permits 20 lookups per day. A free account permits 50 per day and 500 per month. The unlimited plan costs $4.99 per month and allows unlimited lookups, subject to a limit of 10,000 new keywords per day. The MCP service and HTTP API draw from the same key and quota.

Results depend on the selected country, so agents should provide the intended market rather than relying on the default. The service is remote, and the repository does not provide server code to run locally. API keys should not be exposed in shared configuration or public URLs.

_Full upstream README: https://allmcps.com/mcp/seodata-dev-keyword-search-volume/readme_