Skip to main content
Glama
Rapid URL Indexer MCP Server

Rapid URL Indexer MCP Server

by jphyqr

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

Related MCP server: gsc-mcp

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 history

  • indexer://apps - List of tracked apps with summary stats

Local Storage

Data is stored in ~/.rapid-indexer/:

  • history.json - All submissions, app tracking, monthly usage

  • config.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

Available Tools

8 tools
check_balanceA

Get current Rapid URL Indexer credit balance.

Inputs: no named parameters.

get_historyA

Get submission history from local tracking. Shows summary stats, per-app breakdowns, and recent submissions.

Inputs: days, app_name.

get_project_statusC

Get detailed status for a specific indexing project.

Inputs: project_id (required).

get_reportA

Download indexing report for a project showing which URLs were indexed.

Inputs: project_id (required).

get_statsB

Get overall statistics and usage tracking. Includes projections toward 50k/year goal.

Inputs: period.

list_projectsB

List all indexing projects from the Rapid URL Indexer API.

Inputs: limit, status, app_name.

submit_sitemapA

Parse and submit URLs from a sitemap.xml file. Automatically deduplicates against previously submitted URLs. Supports filtering by regex pattern.

Inputs: app_name (required), sitemap_url (required), limit, apex_mode, +3 more.

submit_urlsA

Submit URLs for Google indexing via Rapid URL Indexer. Each URL costs 1 credit (or 3 in Apex Mode for faster indexing). URLs are tracked to prevent duplicate submissions.

Inputs: urls (required), app_name (required), notify, apex_mode, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct function: submitting URLs, submitting sitemaps, checking balance, managing projects, and retrieving reports/history/stats. There is no overlap or ambiguity between tool purposes.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., submit_urls, get_report, list_projects). No mixed conventions or irregular naming.

    Tool Count5/5

    8 tools is well-scoped for the service, covering submission, monitoring, and reporting without unnecessary bloat or missing essentials.

    Completeness5/5

    The tool set covers the full lifecycle: submit individual URLs or sitemaps, check credits, list and inspect projects, download reports, and review local history/stats. No obvious dead ends or critical missing operations for the stated purpose.

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables programmatic management of Google Search Console properties and IndexNow URL submission for search indexing.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP hosts to submit URLs to Googlebot, check indexing status, read task results, and launch traffic or CTR campaigns using the Rapid Indexer API.
      12
      31 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to push changed URLs to search engines such as Bing, Yandex, Seznam, Naver, and Yep. Currently it is a scaffold and does not yet call any search engine.
      Apache 2.0