Rankparse MCP Server
SEO MCP server — backlinks, domain authority, tech stack, and 18+ tools via Common Crawl.
What is the Rankparse MCP Server?
The Rankparse MCP server gives AI agents structured, permission-aware access to Rankparse through the Model Context Protocol. With 43 pre-built actions, agents can read, create, and update Rankparse data on behalf of authorized users.
Willow ships the Rankparse MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how Rankparse is being used by every AI agent in your stack.
Tools
get_backlinks
Get backlinks for a domain. Default sort=importance returns aggregated referrer rows; sort=recent returns URL-level freshest links. Optional filters: from_domain, link_type, score.
get_referring_domains
Get unique domains linking to a domain
get_outbound_links
Get domains that a domain links out to
get_domain_authority
Get authority score for a domain
get_domain_rank
Get inbound edge count and linking domain stats
get_anchor_text
Get anchor text distribution for a domain
get_top_pages
Get most-linked pages for a domain
get_domain_overlap
Find domains linking to all queried domains
get_link_intersect
Find domains linking to A but not B
get_similar_domains
Find domains with similar link profiles. May return partial results when the query fan-out hits time budget.
get_sitemap
Discover and parse a domain's sitemap — returns URLs with lastmod, changefreq, and priority
get_crawl_history
Get first/last seen dates and total snapshot count for a domain (source: Wayback Machine)
get_page_seo
Full real-time SEO audit for a URL — title/description with length checks, canonical, robots meta, OG tags, Twitter cards, JSON-LD, hreflang, headings, images missing alt, link counts, word count
get_tech_stack
Real-time technology detection for a domain — frameworks, CMS, analytics, CDN, hosting, e-commerce, payments, and more (50+ technologies)
get_site_health
Real-time site health check — HTTPS enforcement, HSTS, www redirect behavior, key URL availability and response times, security headers (CSP, X-Frame-Options, HSTS), robots.txt analysis
get_schema_markup
Get schema.org markup for a URL (v1 stub)
get_internal_links
Get internal link structure for a domain (v1 stub)
get_link_velocity
Get rate of new/lost links over time (v1 stub)
get_new_links
Get links gained since previous crawl (v1 stub)
get_lost_links
Get links lost since previous crawl (v1 stub)
get_site_explorer
Full SEO overview for a domain (backlinks, authority, top pages, anchor text)
batch_lookup
Get backlinks for up to 50 domains at once
check_credits
Check remaining credit balance
get_platform_domains
Get all domains running a specific platform or technology (e.g. WordPress, Shopify, Wix, Squarespace, Framer). Returns domains with DA scores. Billed at 1 credit per result returned.
get_platform_trends
Get a ranked list of all detectable platforms and technologies with their domain counts — useful for comparing platform adoption (e.g. how many sites run WordPress vs Shopify)
get_gsc_properties
List all Google Search Console properties (sites) connected to this account. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_top_queries
Get the top search queries driving traffic to a site, ordered by clicks. Shows clicks, impressions, CTR, and average position for each query. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_top_pages
Get the top pages on a site by clicks from Google Search, with impressions, CTR, and average position. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_page_queries
Get search queries driving traffic to a specific page. Useful for understanding what a page ranks for. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_query_pages
Get all pages that rank for a specific search query. Useful for identifying which pages compete for the same keyword. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_date_trends
Get daily search performance trends (clicks, impressions, CTR, position) over a date range. Useful for spotting ranking changes, traffic drops, or algorithm update impact. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_country_breakdown
Get search traffic broken down by country. Useful for understanding geographic audience and international SEO performance. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_device_breakdown
Get search traffic broken down by device type (desktop, mobile, tablet). Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_sitemaps
List all submitted sitemaps for a property, including submission date, last download time, URL counts, and any errors or warnings. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_url_inspection
Inspect a specific URL's indexing status in Google Search. Returns whether the page is indexed, coverage state, last crawl time, mobile usability, and rich results status. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_query_page_pairs
Get query+page combinations — which exact queries are landing on which pages. Essential for detecting keyword cannibalization (multiple pages competing for the same query) and understanding the search funnel. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_page_trend
Get daily click/impression/CTR/position trend for a specific page. Use this to see how a single page's search performance has changed over time — useful for measuring the impact of a content update or spotting a ranking drop. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_query_trend
Get daily click/impression/CTR/position trend for a specific search query. Use this to track how a particular keyword's ranking and traffic evolves over time. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_opportunity_queries
Find queries where the site ranks on positions 8–20 (page 1 bottom / page 2) — the "quick win" zone where small improvements can meaningfully increase clicks. Returns queries sorted by clicks descending (GSC API default). Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_low_ctr_queries
Find search queries with high impressions but low CTR — these are ranking but not getting clicked, usually because the title or meta description is weak or misleading. Fixing these is typically higher ROI than chasing new rankings. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_low_ctr_pages
Find pages with high impressions but low CTR — pages that Google is showing frequently but users aren't clicking. Good starting point for title/description rewrites. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_page_segment
Analyze search performance for a URL segment — e.g. all blog posts ("/blog/"), all product pages ("/products/"), or all docs ("/docs/"). Returns the top pages within that segment by clicks. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_search_appearance
Break down traffic by how the site appears in Google Search — organic web results, rich results, AMP, image search, video, news, etc. Shows which search features are driving impressions and clicks. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
Customize Tools
Edit descriptions, modify arguments, select tools, or add new ones
Set Up Your Rankparse MCP Server in Minutes
Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.
Claude Desktop
{
"mcpServers": {
"willow-rankparse": {
"type": "http",
"url": "https://<org>.mcp-s.com/mcp/mcp/rankparse"
}
}
}Cursor
{
"mcpServers": {
"willow-rankparse": {
"type": "http",
"url": "https://<org>.mcp-s.com/mcp/mcp/rankparse"
}
}
}Claude Code
claude mcp add willow-rankparse --transport http https://<org>.mcp-s.com/mcp/mcp/rankparsen8n
{
"url": "https://<org>.mcp-s.com/mcp/mcp/rankparse",
"method": "POST"
}Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.
Enterprise Governance for Rankparse
Willow adds the layer Rankparse and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.
Rankparse MCP Server FAQ
What is the Rankparse MCP server?
The Rankparse MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write Rankparse data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.
How is Willow's Rankparse MCP server different from the official one?
The official Rankparse MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.
Which AI clients work with the Rankparse MCP server?
Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.
Is the Rankparse MCP server secure? How does Willow handle authentication?
Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in Rankparse, nothing more. No credentials reach the LLM. Every action writes to an audit trail.
Can I limit which Rankparse actions agents can take?
Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.
How do I detect shadow Rankparse MCP servers in my org?
Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved Rankparse MCP locally, you'll see it.
What does the Rankparse MCP server cost?
Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.
How do I install the Rankparse MCP server with Willow?
Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.
Compare Willow MCP Gateway
See how Willow stacks up against other MCP platforms on governance, security, and enterprise readiness.
Your agents are already in the wild.
Give them a Basecamp. Go from AI chaos to AI work, in minutes.