MCP server
Give your AI assistant native tools over your Rankealo domain — calendar, GSC, visibility, publish — via the Model Context Protocol.
Install#
From your project directory (or use the in-app MCP setup at /mcp):
bash
npx @rankealo/mcp-server mcp initThe init flow writes MCP config for Claude Code, Cursor, Windsurf, or Codex and prompts for your domain-scoped API key.
Environment variables the server expects:
env
RANKEALO_API_KEY=rnk_your_key_here
RANKEALO_BASE_URL=https://app.rankealo.aiRead tools (read-scoped keys)#
- get_content_calendar · get_articles · get_article_details
- get_gsc_overview · get_gsc_opportunities
- get_llm_visibility · get_seo_health · get_keyword_pool
- get_settings · get_data_freshness
- get_site_performance_summary · get_content_brief · get_geo_health · get_visibility_score
- get_llm_responses · get_competitor_intel · get_refresh_candidates · …
Write tools (write-scoped keys, Growth)#
- publish_article
- reschedule_article · set_article_status
- chat_seo_agent
- update_autopublish · update_content_preferences · update_seo_agent_settings · update_internal_linking
Scope gating
Write tools call the same POST/PATCH API routes as the REST API. Read-only keys receive 403 on mutating tools.Related#
Product overview and GitHub App coding agent: /for-agents. In-app setup workspace: /mcp.
Still stuck? Contact support
