rapid-indexer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host to bind for HTTP mode. | 127.0.0.1 |
| PORT | No | Port to bind for HTTP mode. | 3333 |
| MCP_PATH | No | Path for the MCP endpoint in HTTP mode. | /mcp |
| RAPID_INDEXER_API_KEY | Yes | Required for stdio. Fallback only in HTTP mode. | |
| RAPID_INDEXER_BASE_URL | No | Base URL of the Rapid Indexer API. | https://rapid-indexer.com/api/v1/index.php |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_accountA | Return the authenticated Rapid Indexer account (id, email, credits balance, created date). Use it to check credits before creating tasks. |
| get_pricingA | Return live credit costs: credits per URL for standard/VIP indexing and index checking, traffic price per 1,000 visitors, USD per credit, and whether VIP/traffic are currently enabled. |
| estimate_costA | Estimate the credit and USD cost of an indexing or index-check task before submitting it, and whether the account balance covers it. Does not create anything. |
| submit_urls_for_indexingA | Create an indexing task: Rapid Indexer signals Googlebot to crawl each URL so Google discovers it fast. SPENDS CREDITS immediately (standard ~2 credits/URL, VIP ~10 credits/URL). Run estimate_cost first and confirm with the user for large batches. Standard queue starts within minutes; VIP starts immediately with priority. drip_feed spreads submissions over several days for a natural pattern. Returns the task id; poll get_task for progress and get_task_links for per-URL status. Google makes the final indexing decision. |
| check_index_statusA | Create an index-check task that reports, per URL, whether Google currently has it in the index (indexed / unindexed). Cheap (~0.1 credit per URL) but still SPENDS CREDITS. Results arrive within a few minutes: poll get_task, then read get_task_links. Does not submit anything to Google; use submit_urls_for_indexing for that. |
| list_tasksA | List the account's tasks, newest first, with per-link counts (indexed / unindexed / pending / error). Filter by type or status. Use it to find task ids. |
| get_taskA | Fetch one task, refreshing its status from the provider first. Returns status (pending/processing/completed/failed) and progress counts. Poll this after creating a task. |
| get_task_linksA | Return each URL in an indexing or index-check task with its status (indexed / unindexed / pending / error). Filter by status and paginate with limit/offset for big tasks. Always includes a summary count. |
| create_traffic_campaignA | Send AI-driven, human-like visitors to a URL (geo, device, referrer and on-page behaviour are configurable). SPENDS CREDITS immediately: see get_pricing (credits per 1,000 visitors). visitors/days must not exceed 1,000 per day. Confirm with the user before creating. Returns the task id; poll get_task for status. |
| create_ctr_campaignA | Send visitors who search the given keywords on a search engine (Google by default), find the target URL in the results and click it, then browse like a human. SPENDS CREDITS immediately (same rate as traffic, per visitor). Confirm with the user before creating. Use list_search_engines for valid search_engine values. |
| list_search_enginesA | Return the search engines and marketplaces accepted by create_ctr_campaign.search_engine. |
| check_service_healthA | Ping the Rapid Indexer API and report version and enabled features (indexer, checker, traffic, ctr). Also validates that the configured API key works. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| index_and_verify | Guided workflow: estimate cost, submit URLs for indexing, and explain how to verify results. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.