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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.