Rapid Indexer

com.rapid-indexerv0.1.0Updated Oct 8, 2026

Send new pages and backlinks to Googlebot fast, then check which URLs Google has indexed.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Lets an assistant submit URLs to Googlebot for indexing, check whether pages are indexed, and run traffic or CTR campaigns.

What it does
Submits up to 10,000 URLs per indexing task to Googlebot, with standard or VIP queues and optional drip feed, and creates index-check tasks that report per-URL indexed or unindexed status. It also lists tasks, refreshes task progress, and returns per-URL results with filtering and pagination. Account, pricing and cost-estimation tools report credit balance and the cost of a batch before spending. Campaign tools create AI traffic campaigns and CTR campaigns that search keywords on chosen search engines and click the result.
When to use it
Use it when you publish or update pages and want them crawled quickly, or when you need to confirm which URLs Google has actually indexed. It also fits workflows that estimate indexing cost before submitting a batch, or that run traffic and CTR campaigns for a URL. The index_and_verify prompt guides an estimate, submit and verify sequence.
Requirements
A Rapid Indexer account and API key, obtained from the account's API Access page. The hosted endpoint is reached at with the key in the Authorization header. For local use, Node.js 20 or newer and the rapid-indexer-mcp npm package, with the key in RAPID_INDEXER_API_KEY. Network access to the Rapid Indexer API is required.
Before you install
Requires a Rapid Indexer API key sent as the Authorization header (Bearer) or RAPID_INDEXER_API_KEY; treat it as a secret. Several tools spend account credits: submit_urls_for_indexing, check_index_status (about 0.1 credits per URL), create_traffic_campaign and create_ctr_campaign, so costs can accumulate. Traffic and CTR campaigns generate artificial visitors and clicks, which may conflict with search engine policies. The server sends your URLs and account data to the Rapid Indexer API.

Installation

In SourceWeft

  1. Open Rapid Indexer in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.rapid-indexer.com/mcp"
    }
  }
}

README

rapid-indexer-mcp

Model Context Protocol server for Rapid Indexer. It lets Claude, Cursor, ChatGPT, Claude Code and any other MCP host submit URLs to Googlebot, check whether pages are indexed, read task results and launch traffic / CTR campaigns using your Rapid Indexer API key.

Built on the official TypeScript SDK v2 (@modelcontextprotocol/server). Serves over stdio (local, one account) or Streamable HTTP (hosted, multi-tenant: each request carries its own API key).

Requirements

  • Node.js 20+
  • A Rapid Indexer API key: log in, open your account menu → API Access (https://rapid-indexer.com/api_access).

Quick start (stdio)

Cursor

~/.cursor/mcp.json (or .cursor/mcp.json in a project):

json
{
  "mcpServers": {
    "rapid-indexer": {
      "command": "npx",
      "args": ["-y", "rapid-indexer-mcp"],
      "env": { "RAPID_INDEXER_API_KEY": "YOUR_API_KEY" }
    }
  }
}

Claude Desktop

~/.config/Claude/claude_desktop_config.json on Linux:

json
{
  "mcpServers": {
    "rapid-indexer": {
      "command": "npx",
      "args": ["-y", "rapid-indexer-mcp"],
      "env": { "RAPID_INDEXER_API_KEY": "YOUR_API_KEY" }
    }
  }
}

Claude Code

bash
claude mcp add rapid-indexer -e RAPID_INDEXER_API_KEY=YOUR_API_KEY -- npx -y rapid-indexer-mcp

From a local checkout (before publishing to npm)

bash
cd mcp
npm install
npm run build

Then point the host at the built CLI:

json
{
  "mcpServers": {
    "rapid-indexer": {
      "command": "node",
      "args": ["/absolute/path/to/Rapid-Indexer-main/mcp/dist/cli.js"],
      "env": { "RAPID_INDEXER_API_KEY": "YOUR_API_KEY" }
    }
  }
}

Hosted mode (Streamable HTTP)

One process serves every customer; the API key travels with each request.

bash
RAPID_INDEXER_BASE_URL=https://rapid-indexer.com \
node dist/cli.js --http --host 0.0.0.0 --port 3333 --path /mcp

Clients connect to https://your-host/mcp and send Authorization: Bearer <api key> (also accepted: X-API-Key: <key>, or ?api_key= on the URL). GET /healthz returns a liveness JSON.

Cursor example for a remote server:

json
{
  "mcpServers": {
    "rapid-indexer": {
      "url": "https://mcp.rapid-indexer.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Put it behind TLS (nginx/Caddy) and run it with systemd or pm2. The server is stateless, so you can run several replicas. --api-key / RAPID_INDEXER_API_KEY in HTTP mode is only a fallback for requests that carry no key (single-tenant self-hosting).

Tools

ToolSpends creditsWhat it does
get_accountnoAccount id, email, credit balance (+ USD).
get_pricingnoLive credits per URL (standard / VIP / checker), traffic price per 1,000 visitors, USD per credit.
estimate_costnoCost of N URLs as indexer/checker (+VIP) and whether the balance covers it.
submit_urls_for_indexingyesCreate an indexing task (standard or VIP queue, optional drip feed). Max 10,000 URLs.
check_index_statusyes (~0.1 cr/URL)Create an index-check task: per-URL indexed / unindexed.
list_tasksnoPaginated task list with indexed/unindexed/pending/error counts; filter by type/status.
get_tasknoRefresh and return one task's status and progress.
get_task_linksnoPer-URL results with status filter and pagination.
create_traffic_campaignyesAI visitors to a URL (geo, device, referrer, behaviour).
create_ctr_campaignyesVisitors search keywords on Google/Bing/… and click your result.
list_search_enginesnoValid search_engine values for CTR campaigns.
check_service_healthnoAPI version, enabled features, and confirms the key works.

Every tool returns human-readable text plus structuredContent validated by an output schema. Errors from the API come back as isError results with the API message and a hint (top-up link on insufficient credits, key location on 401).

Prompt: index_and_verify — guided estimate → submit → verify workflow.

Environment / flags

VariableFlagDefaultNotes
RAPID_INDEXER_API_KEY--api-key–Required for stdio. Fallback only in HTTP mode.
RAPID_INDEXER_BASE_URL--base-urlhttps://rapid-indexer.com/api/v1/index.phpSite origin is also accepted; the router path is appended.
HOST--host127.0.0.1HTTP mode.
PORT--port3333HTTP mode.
MCP_PATH--path/mcpHTTP mode.

Development

bash
npm install
npm run build          # tsc → dist/
npm run dev            # run src/cli.ts with tsx (stdio)
npm run inspect        # MCP Inspector against dist/cli.js

If npm install hangs on a machine with broken IPv6, run it with NODE_OPTIONS="--no-network-family-autoselection --dns-result-order=ipv4first".

Publishing

bash
npm version patch
npm publish --access public

prepublishOnly builds dist/. The package ships only dist/, README.md and LICENSE.

API coverage

The server talks to the public REST API documented at https://rapid-indexer.com/api-docs. list_tasks and pricing were added to that API together with this server; hosts running an older build of the site will see those two tools fail with "Invalid action" until the API is redeployed.

License

MIT

Source: README.md at commit c314719

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.1.0LatestOct 8, 2026