rapid-indexer-mcp
Related Servers
Alternatives to rapid-indexer-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP clients to query Search Analytics metrics, list and inspect properties and sitemaps, and inspect indexed URLs with secure authentication and optional allowlisted write controls.6MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to run Google Search, News, and Local queries and receive structured organic results, news, and local packs as JSON.-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables interacting with Google's Indexing API, allowing agents to submit URLs to Google for indexing or removal from search results through natural language commands.-
- AlicenseAqualityBmaintenanceEnables MCP clients to retrieve Search Console search analytics, find multilingual question-shaped queries and SEO opportunities, inspect URLs, and view or manage sitemaps with server-side date resolution and comparisons.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables interaction with Google Search Console via MCP, offering search analytics, performance summaries, URL inspection, sitemap management, and property listing for SEO workflows.273 npm1MIT
- AlicenseBqualityBmaintenanceEnables Google Search Console data queries via MCP, including search analytics, performance comparisons, URL inspection, and sitemap management.121MIT
TDQS
Scored across 12 tools
Each tool targets a distinct action or resource: account, pricing, cost estimation, indexing submission, index checking, task listing, task details, per-link results, traffic campaigns, CTR campaigns, search engine listing, and health checks. The few similar-looking tools (create_traffic_campaign vs. create_ctr_campaign, get_task vs. get_task_links) are clearly differentiated by their descriptions and intended workflow.
All tool names follow a consistent verb_noun pattern in lower_snake_case, such as get_account, submit_urls_for_indexing, list_tasks, and create_ctr_campaign. The naming clearly indicates both the action and the resource, making the set predictable and easy to navigate.
With 12 tools, the server is well-scoped for its purpose. Each tool earns its place by covering account management, pricing/cost estimation, task creation, task monitoring, and campaign setup without unnecessary bloat.
The tool set covers the core lifecycle thoroughly: estimate costs, submit indexing or index-check tasks, poll task status, and inspect per-URL results. Minor gaps exist, such as no dedicated campaign performance metrics beyond generic task polling and no cancellation/update operations, but these can be worked around and do not severely hinder the main workflows.