Indexer MCP. Manage bulk URLs without touching the console.

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.