It remembers, because it tracks
Most SEO MCP servers query data live, one question at a time. LemRank checks your keywords every day, so the assistant can answer what changed since last week rather than only what is true right now.
Model Context Protocol
An SEO MCP server that actually tracks your rankings
Give Claude, ChatGPT or Cursor direct access to your Google positions. Ask what moved, what is cannibalising what, and what to track next — answered from your own daily rank data, not from a live guess.
Install
Connect it in under a minute
- Create an API key in LemRank: sign in, open REST API Documentation (
/api-docs) and use the API Keys tab. The key is shown once and stored only as a hash. - Add the server below to your assistant and paste the key in place of
YOUR_LEMRANK_API_KEY. - Ask it something like “which of my keywords dropped this week?”
Endpoint
https://lemrank.com/api/public/mcp
Claude Desktop, Cursor, Windsurf and other clients that read a JSON config
{
"mcpServers": {
"lemrank": {
"url": "https://lemrank.com/api/public/mcp",
"headers": {
"Authorization": "Bearer YOUR_LEMRANK_API_KEY"
}
}
}
}Claude Code
claude mcp add --transport http lemrank https://lemrank.com/api/public/mcp \ --header "Authorization: Bearer YOUR_LEMRANK_API_KEY"
In ChatGPT, add it as a remote connector using the same endpoint and put the key in an Authorization: Bearer header. Any client that speaks Streamable HTTP MCP will work — the server holds no session state. The same data is available over REST.
Tools
What the assistant can do
| Tool | What it returns |
|---|---|
| list_projects | Every site the API key tracks, with its domain, tracking frequency, default language and default location. |
| get_project | One tracked site, checked against the key's owner. |
| list_keywords | Current Google positions, previous and best position, ranking URL, volume, CPC and difficulty. |
| ranking_history | Up to 90 days of daily positions, so the assistant can describe movement rather than guess. |
| serp_snapshots | Whether an AI Overview, featured snippet or local pack was present when the result page was captured. |
| track_keyword | Add a keyword to tracking. Returns the existing one instead of creating duplicates. |
| url_intel | For one URL you own: ranking keywords, 30-day sparklines, cannibalisation, toxic backlink count and AI citations. |
| whoami | Confirm which account the configured key belongs to. |
What it does not do: it has no site crawler and no third-party backlink index of its own. For a technical crawl, pair it with a crawler MCP — we say which ones in the roundup.
Why this one
Tracking data beats live lookups
Ninety days of history per call
Daily positions come back as a series, which is what an assistant needs to spot a slide before it becomes a crisis.
Scoped to your account
Every call carries your own API key and is re-checked against the account that owns each project. A key can never read another workspace.
No install, no local process
It is a remote server over Streamable HTTP. Nothing to run on your machine, nothing to keep awake for a scheduled task.
In practice
Things to ask it
- Which keywords dropped more than five places this week?
- Summarise the ranking trend for my top twenty keywords over the last 30 days.
- Which of my pages are competing for the same keyword?
- Track these fifteen keywords for me.
- Which tracked keywords show an AI Overview on the results page?
Check it works
Call it directly
List the tools with curl
curl -X POST https://lemrank.com/api/public/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "Authorization: Bearer YOUR_LEMRANK_API_KEY" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Rate limits and error codes match the REST API: 60 requests a minute per key, and a clear message when a key is missing, expired or out of quota.
Start tracking, then plug it in
The MCP server reads whatever LemRank is tracking for you, so the first step is adding your keywords. The trial is free and needs no card.