Rapid URL Indexer MCP Server
Enables submitting URLs to the Rapid URL Indexer API, tracking submissions across projects, and auto-detecting new pages from sitemaps.
README
Rapid URL Indexer MCP Server
An MCP (Model Context Protocol) server for submitting URLs to the Rapid URL Indexer API. Track submissions across multiple projects, monitor indexing progress, and auto-detect new pages from sitemaps.
Target: 50,000 pages/year across 10+ apps
Features
- Submit individual URLs or entire sitemaps for Google indexing
- Track all submissions across multiple projects/apps
- Automatic deduplication of already-submitted URLs
- Monitor indexing progress and credit usage
- View statistics and projections toward goals
Installation
# Clone the repository
git clone https://github.com/jphyqr/rapid-indexer-mcp.git
cd rapid-indexer-mcp
# Install dependencies
npm install
# Build
npm run build
Configuration
API Key
Set your Rapid URL Indexer API key via environment variable:
export RAPID_INDEXER_API_KEY=your-api-key
Or create a config file at ~/.rapid-indexer/config.json:
{
"apiKey": "your-api-key",
"defaultApexMode": false,
"defaultNotify": false,
"apps": {}
}
Claude Code MCP Config
Add to your Claude Code MCP configuration (~/.claude/mcp.json or VS Code settings):
{
"mcpServers": {
"rapid-indexer": {
"command": "node",
"args": ["/path/to/rapid-indexer-mcp/dist/index.js"],
"env": {
"RAPID_INDEXER_API_KEY": "your-api-key"
}
}
}
}
Tools
submit_urls
Submit URLs for indexing.
Submit these URLs to the indexer for vancouversublets:
https://vancouversublets.com/listing/123
https://vancouversublets.com/listing/456
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
urls |
string[] | Yes | Array of URLs to index |
app_name |
string | Yes | Project/app identifier |
project_name |
string | No | Optional batch name |
apex_mode |
boolean | No | 3 credits/URL, faster indexing |
notify |
boolean | No | Email notifications |
submit_sitemap
Parse and submit URLs from a sitemap.xml file.
Submit new pages from vancouversublets.com sitemap, only listing pages
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
sitemap_url |
string | Yes | URL to sitemap.xml |
app_name |
string | Yes | Project/app identifier |
filter_pattern |
string | No | Regex to include URLs |
exclude_pattern |
string | No | Regex to exclude URLs |
skip_already_submitted |
boolean | No | Skip duplicates (default: true) |
limit |
number | No | Max URLs to submit |
apex_mode |
boolean | No | Enable Apex Mode |
check_balance
Get current credit balance.
What's my indexing credit balance?
list_projects
List all indexing projects.
Show me all my indexing projects for vancouversublets
get_project_status
Get detailed status for a project.
What's the status of project 123?
get_report
Download indexing report showing which URLs were indexed.
Get the indexing report for project 123
get_history
Get local submission history.
Show my indexing history for the last 7 days
get_stats
Get statistics and usage tracking.
How's my indexing going this month?
Resources
The server exposes two MCP resources:
indexer://history- Full submission historyindexer://apps- List of tracked apps with summary stats
Local Storage
Data is stored in ~/.rapid-indexer/:
history.json- All submissions, app tracking, monthly usageconfig.json- API key and app configurations
Example Workflows
Daily New Page Indexing
User: "Submit new pages from vancouversublets sitemap"
Claude: Uses submit_sitemap with skip_already_submitted=true
- Fetches sitemap
- Compares against history
- Submits only new URLs
Bulk Initial Indexing
User: "Index all listing pages from vancouversublets, use apex mode"
Claude: Uses submit_sitemap with filter_pattern="/listing/", apex_mode=true
- Submits all matching URLs
- Uses 3 credits per URL for faster indexing
Check Progress
User: "How's my indexing going this month?"
Claude: Uses get_stats with period="month"
- Shows submitted vs indexed
- Shows by-app breakdown
- Shows if on track for 50k goal
Development
# Watch mode
npm run dev
# Build
npm run build
# Run directly
npm start
License
MIT
Author
John Hashem john@hashbuilds.com
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。