
Rapid Indexer
com.rapid-indexerv0.1.0更新於 Oct 8, 2026
Send new pages and backlinks to Googlebot fast, then check which URLs Google has indexed.
概覽
讓助理把網址提交給 Googlebot 以加快收錄、檢查頁面是否已被 Google 收錄,並執行流量或 CTR 活動。
- 功能
- 每個收錄任務最多可向 Googlebot 提交 10,000 個網址,可選標準或 VIP 佇列以及滴灌式投放,並建立收錄檢查任務,依網址回報已收錄或未收錄。也可列出任務、重新整理任務進度,並依狀態篩選與分頁回傳每個網址的結果。帳戶、價格與費用估算工具會回報額度餘額以及一批網址的花費,方便在消費前評估。活動工具可建立 AI 流量活動,以及讓訪客在指定搜尋引擎搜尋關鍵字並點擊結果頁的 CTR 活動。
- 適用情境
- 適合在發布或更新頁面後希望盡快被抓取,或需要確認 Google 實際收錄了哪些網址時使用。也適合在提交批量網址前估算收錄成本,或為某個網址執行流量與 CTR 活動。index_and_verify 提示會引導完成估算、提交與驗證流程。
- 執行需求
- 需要 Rapid Indexer 帳戶與 API 金鑰,可從帳戶的 API Access 頁面取得。託管端點為 Authorization 標頭中。本機執行需要 Node.js 20 以上版本以及 rapid-indexer-mcp npm 套件,金鑰放在 RAPID_INDEXER_API_KEY 中。需要能連線至 Rapid Indexer API 的網路。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Rapid Indexer,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"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):
Claude Desktop
~/.config/Claude/claude_desktop_config.json on Linux:
Claude Code
From a local checkout (before publishing to npm)
Then point the host at the built CLI:
Hosted mode (Streamable HTTP)
One process serves every customer; the API key travels with each request.
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:
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
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
Development
If npm install hangs on a machine with broken IPv6, run it with
NODE_OPTIONS="--no-network-family-autoselection --dns-result-order=ipv4first".
Publishing
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
來源:README.md,提交 c314719
工具
0版本歷史
1- v0.1.0最新Oct 8, 2026
