# Indexer MCP > The Rapid URL Indexer Alternative MCP Server lets you automate Google Search Console indexing directly through your AI agent. Submit huge batches of URLs, track progress in real-time, and manage project credits—all without leaving your workflow. It handles the heavy lifting of SEO submissions, so you don't have to manually check dashboards or wait for slow webmaster tools. ## Overview - **Category:** developer-tools - **Price:** Free - **Tags:** google-indexing, search-console, url-submission, seo-automation, webmaster-tools ## Description Listen up. This MCP server lets your AI client bypass the slow webmaster tools and handle Google Search Console submissions directly. You're dealing with large-scale SEO projects here—site migrations, major content dumps, link building campaigns—and you need speed, accuracy, and control. Forget manually checking dashboards or waiting for whatever crawl budget they give you; this thing handles the heavy lifting so your agent can manage it all within your existing workflow. **Checking Your Funds First:** Before you even think about sending a batch of URLs, you gotta know what you're working with. You use the `get_credit_balance` tool to query your account and see exactly how many credits you've got left for submissions. It’s quick—you just need to check that balance first so you don't hit a paywall halfway through a critical project. **Seeing What's Running:** When you start running multiple indexing jobs, you gotta keep track of 'em. The `list_projects` tool gives you an immediate rundown of every single indexing job associated with your account—whether it's pending, submitted, or already finished. You'll get a clean list so you know exactly what projects are currently active and which ones need attention. **Kicking Off the Submission:** Ready to submit? The `submit_project` tool lets you create and launch an entirely new indexing job. This is where the action happens: you can send huge batches of URLs, up to 9,999 in a single go. If speed is your main concern and you're willing to burn some credits, you can opt for **Apex mode**. That setting boosts your crawling speed and attempts, making sure those critical pages get noticed fast. **Watching the Progress:** Launching a job doesn't mean you can walk away. You need updates. When you use `get_project_status`, you feed it a specific project ID, and it returns detailed, real-time progress updates for that one job. It tells you if the project is stalled, if it's running smoothly through its queue, or what the current status is right now. **Getting the Final Scorecard:** Once a project wraps up—and only when it’s truly done—you gotta know how every single URL performed. You use `get_project_report` to download a full report. This isn't just a vague 'completed' message; this provides the indexing status for *every* single URL that was submitted in that project, giving you a clean data set of results. It’s all about automation control. You use your agent to first check your credit balance with `get_credit_balance`, then list existing projects using `list_projects` so you don't mess up an active job, and finally, when it's time for a big push, the `submit_project` tool handles the submission of up to 9,999 URLs. You monitor that new launch with `get_project_status`, watching its real-time progress until the job is done, after which you pull all the necessary data by running `get_project_report` to get a final status report for every single piece of content. ## Tools ### get_credit_balance Checks your remaining credit balance for the service. ### get_project_report Downloads a final report showing the indexing status for every URL in a project. ### get_project_status Gets detailed, real-time progress and status updates for a specific project ID. ### list_projects Shows a list of all indexing projects you've created or are tracking. ### submit_project Creates and submits a new URL batch for indexing, allowing for priority crawling via Apex mode. ## Prompt Examples **Prompt:** ``` Submit these URLs for indexing in a project named 'New Backlinks': https://example.com/page1, https://example.com/page2 ``` **Response:** ``` I've submitted your project 'New Backlinks' with 2 URLs. The project ID is 12345. You can check its status later using `get_project_status`. ``` **Prompt:** ``` Check my current credit balance on Rapid URL Indexer. ``` **Response:** ``` You currently have 1,500 credits available in your account. ``` **Prompt:** ``` List all my indexing projects and show me the status of the most recent one. ``` **Response:** ``` I've retrieved your projects. Your most recent project 'Blog Update' (ID: 54321) is currently 'completed'. ``` ## Capabilities ### List all projects Retrieves a list of every indexing project associated with your account. ### Submit URL batch Starts a new indexing job using up to 9,999 URLs. Apex mode costs credits but boosts speed and attempts. ### Get project status Returns the detailed progress (status) for one specific, existing project ID. ### Retrieve full report Downloads a comprehensive status report containing the indexing result for every single URL in a finished project. ### Check credit balance Queries your account to show how many credits you have left for submissions. ## Use Cases ### The post-migration checkup A developer just pushed 500 new pages. Instead of submitting them one by one, they ask the agent to run `submit_project` with the entire list and Apex mode. Later, they use `get_project_status` until it hits 'completed', confirming the whole batch was accepted. ### Tracking client backlink dumps A marketing manager needs to track 12 different projects for various clients. They run `list_projects` once, see all IDs, and then use `get_project_status` iteratively to report the completion status to the client. ### Debugging indexing failures A site has failed to index several pages. The user runs `submit_project` on a small batch of problematic URLs, and then uses `get_project_report`. This report pinpoints exactly which URL failed and why. ### Pre-campaign budget check Before running a major content push that costs credits, the SEO specialist checks their limits by asking for `get_credit_balance`. This prevents hitting an unexpected rate limit mid-project. ## Benefits - Start with `list_projects` to see all your current indexing jobs in one view. You don't have to log into a separate dashboard just to check if 'Project Alpha' is done. - When you submit new content, use `submit_project` to send up to 9,999 URLs at once. This handles massive site migrations—not single pages. - Need status updates? Running `get_project_status` gives you the current progress of a project instantly. It tells you if it's pending or actively crawling right now. - Don't guess how many submissions you have left. Just ask your agent to run `get_credit_balance` and know exactly what you can afford before hitting submit. - After 96 hours, use `get_project_report`. This tool pulls together the final status for every single URL so you don't have to wait weeks for a manual report. ## How It Works The bottom line is: your AI client handles the API key management and function calling; you just talk to it about what indexing needs doing. 1. First, subscribe to the server and pass your Rapid URL Indexer API Key. 2. Next, prompt your AI agent with a command like 'List all projects' or 'Submit these URLs for indexing'. 3. Your agent calls the relevant tool (e.g., `submit_project`), gets the project ID, and reports back the status directly in the chat. ## Frequently Asked Questions **How many URLs can I submit with `submit_project`?** You can submit up to 9,999 URLs in a single project batch. This is crucial for site migrations or large backlink builds. **What do I use if a project isn't finished yet? Do I run `get_project_report`?** No, don't run `get_project_report` until the job is done. If it’s still running, you'll get an error (425 Too Early). Use `get_project_status` instead to wait for completion. **How do I check my credit balance?** Just ask the agent to run `get_credit_balance`. It immediately tells you how many credits are left, so you don't accidentally overspend on Apex mode. **If I need a status update on an old project, what should I use?** You first run `list_projects` to get the Project ID. Then, pass that specific ID into `get_project_status` for the most accurate, current status report. **I need to see all my past indexing jobs; should I use the `list_projects` tool?** Yes, running `list_projects` shows every project associated with your account. This lets you gather IDs and check if any projects are pending or complete before checking individual statuses. **What is the cost structure when I use `submit_project`, specifically for Apex Mode?** Apex Mode costs 3 credits per URL submitted. This fee includes up to three indexing attempts, making it ideal for critical pages that need immediate attention. **When I run `get_project_report`, what should I expect if the tool returns a '425 Too Early' error?** A 425 error means the report isn't compiled yet. The data processing takes time, so wait until the designated period has passed before running `get_project_report` again. **What is the maximum number of URLs I can submit in a single batch using `submit_project`?** You can submit up to 9,999 URLs in one project. This bulk submission capacity handles large site migrations and comprehensive backlink indexing. **How many URLs can I submit in a single project?** You can submit an array of up to 9,999 URLs using the `submit_project` tool. Each URL must start with http or https. **What is Apex Mode and how do I enable it?** Apex Mode is a high-priority indexing feature that costs 3 credits per URL. You can enable it by setting the `apex_mode_enabled` parameter to true when calling `submit_project`. **When will my indexing report be available for download?** Reports are available 4 days (96 hours) after the project is created. Use the `get_project_report` tool with your Project ID to retrieve it.