Ask your AI assistant about your App Store rankings

If you build apps with an AI assistant, you shouldn't have to switch to a dashboard to find out how your keywords are doing. The Rankglass MCP server lets the assistant read your Rankglass data directly, so you can ask things like:

• "Which of my keywords dropped this week?"
• "Where does my app rank for dream journal in Germany, and who's above me?"
• "What did my competitors change on their store pages this month?"
• "What's my ASO score, and what should I fix first?"

The assistant answers from the ranks Rankglass checked, not from what it remembers about the stores.

What the assistant can see

The MCP server has nine read-only tools:

• list_apps: your apps, their stores, tracked countries and this week's headline numbers
• get_keyword_rankings: every tracked keyword with rank, 7-day change, best rank, estimated monthly searches, difficulty and competitor ranks
• get_rank_changes: the biggest gains and losses over the last few days, and keywords that entered or left the top 10
• get_competitors: ratings, head-to-head counts and keyword gaps where a competitor is in the top 10 and you aren't
• get_competitor_keywords: the keywords a competitor ranks for in any country you track, including the ones you don't track yet, with monthly searches and both ranks
• get_competitor_insights: a competitor's first release date, price and in-app purchases, chart ranks, rough monthly downloads and revenue, and what its reviewers complain about
• get_store_page_changes: recent title, subtitle, description, screenshot and version changes for your app and your competitors
• get_aso_score: your 0–100 ASO score, the checks behind it and quick keyword wins
• get_weekly_brief: your app's latest weekly AI brief: what changed, the likely reasons and what to do next

It can't change anything in your workspace.

Set it up

MCP and API access are part of the Pro and Agency plans.

1. In Rankglass, open Settings → Workspace → API & MCP and create a key. Copy it right away; it's shown only once.
2. Add the server to your assistant. Replace YOUR_API_KEY with your key.

Claude Code

claude mcp add --transport http rankglass https://app.rankglass.com/api/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Cursor (~/.cursor/mcp.json)

{
	"mcpServers": {
		"rankglass": {
			"url": "https://app.rankglass.com/api/mcp",
			"headers": { "Authorization": "Bearer YOUR_API_KEY" }
		}
	}
}

Claude Desktop (claude_desktop_config.json, needs Node.js)

{
	"mcpServers": {
		"rankglass": {
			"command": "npx",
			"args": [
				"-y",
				"mcp-remote",
				"https://app.rankglass.com/api/mcp",
				"--header",
				"Authorization:${RANKGLASS_AUTH}"
			],
			"env": { "RANKGLASS_AUTH": "Bearer YOUR_API_KEY" }
		}
	}
}

The settings page shows the same snippets with the right address for your account.

Prefer plain HTTP?

The same data is available from a read-only REST API. Every endpoint is a GET under /api/v1 and takes the same key:

curl "https://app.rankglass.com/api/v1/rank-changes?days=7" \
  -H "Authorization: Bearer YOUR_API_KEY"

Endpoints: /v1/apps, /v1/keywords, /v1/rank-changes, /v1/competitors, /v1/competitor-keywords, /v1/competitor-insights, /v1/store-page-changes, /v1/aso-score and /v1/weekly-brief.

Each key can make 60 requests a minute and 2,000 a day across the MCP server and the REST API; past that, requests get a 429 response with a Retry-After header saying how many seconds to wait.

Keep keys safe

A key can read everything in its workspace, so treat it like a password. Create one key per tool so you can revoke them separately; the settings page shows when each key was last used.