Keyword data inside your AI assistant

seodata.dev runs an MCP server, so Claude, ChatGPT, Meta Muse and other assistants can look up Google search volume, CPC and competition while they work. You ask in plain language and the assistant fetches the numbers.

# what is MCP

The Model Context Protocol is an open standard that lets AI assistants call tools hosted by other services. You add a server's URL to your assistant once. After that, whenever a question needs keyword data, the assistant calls seodata.dev on its own and uses the answer.

Our server gives your assistant three tools:

lookup_keyword returns monthly search volume, CPC, competition and similar keywords (with their volumes) for one keyword in one country.
lookup_keywords does the same for up to 25 keywords at once, which is handy for ranking a list of ideas.
get_usage shows your plan and how many lookups you have left.

# the server URL

https://mcp.seodata.dev/mcp

This works straight away with no account, at 20 lookups a day. When you connect with OAuth or an API key, you get your account's limits instead.

If your assistant only offers sign-in after the server asks for it, use https://mcp.seodata.dev/mcp/auth. It's the same server, but it asks for sign-in up front.

# set it up

Claude Code

claude mcp add --transport http seodata https://mcp.seodata.dev/mcp

Then run /mcp inside Claude Code to sign in. To use an API key instead, add --header "Authorization: Bearer sd_live_…".

Claude (web and desktop)

Open Settings → Connectors → Add custom connector, name it seodata.dev, and paste the server URL. Claude opens our sign-in page the first time it needs data.

ChatGPT and dots

Open Settings → Apps, turn on developer mode under Advanced, then create a new app with the server URL and OAuth as the authentication method. Once it's connected, your dots can use it too, since they share the apps connected to your ChatGPT account.

Meta Muse

Ask Muse directly, for example: "Connect to the MCP server at https://mcp.seodata.dev/mcp and use it for keyword research." Muse builds the connector itself and keeps it for later chats.

Any other MCP client

Use the server URL with the Streamable HTTP transport. For authentication, either let the client run OAuth or send your API key as Authorization: Bearer sd_live_…. Clients that only accept a URL can use https://mcp.seodata.dev/mcp?key=sd_live_…, but keep that URL private because it contains your key.

# signing in

When your assistant connects with OAuth, a seodata.dev page asks for your email and sends you a 6-digit code. There's no password. If you're new, entering the code also creates your free account, and the connection shares limits with any API key you already have.

No account: 20 lookups a day
Free account: 50 a day, 500 a month
Unlimited: no cap, $4.99 a month

Each keyword looked up counts as one lookup, including each one in a batch of 25.

# things to ask

"How many people search for 'headless cms' in the US each month?"
"Here are 15 blog post ideas. Rank them by search volume and tell me which have low competition."
"Find keywords similar to 'ai code editor' with at least 1,000 monthly searches."
"Compare the CPC of 'crm software' in the US, UK and Germany."
"How many seodata.dev lookups do I have left today?"

# if something's off

The assistant says you've hit a limit. Sign in through OAuth or add an API key for higher limits, or go unlimited.
It never asks you to sign in. Switch the URL to https://mcp.seodata.dev/mcp/auth.
A keyword comes back with no data. It may be too niche or misspelled; try a broader version.

Prefer plain HTTP? The same data is available as a REST API; see the API docs.