Which AI clients work with it?
Any client that supports remote MCP servers, including Claude Code, Claude, Cursor, Codex, ChatGPT, OpenCode, and Amp. Pick your client above for the exact setup.
Let your AI agent submit pages to Google
Connect the Index My Site MCP server to Claude Code, Cursor, Codex, or any MCP client. Your agent submits new and updated pages as soon as they go live, and tells you which ones are indexed.
Your agent publishes, submits, and reports back
Here is a real session. The agent ships two pages, submits them in one job, and confirms they are indexed the next day.
- You
Publish the 2.4 changelog and the new webhooks guide, then get both indexed.
- Agent
Both pages are live. Submitting them now.
- Tool call
submit_urls({ name: "Release 2.4", urls: [ "https://example.com/changelog/2-4", "https://example.com/docs/webhooks" ] }) - Agent
Job "Release 2.4" is running: 2 URLs sent, 2 credits used. The first Google search is in 24 hours, with a full report around day 5.
- You
Next morning: are the release pages indexed yet?
- Tool call
get_job({ id: "job_..." }) - Agent
Both are indexed. Google found the changelog and the webhooks guide on the first search.
Connect your client in one step
Pick your client and add the server. It lives at https://indexmysite.app/mcp, and your browser opens once so you can sign in and approve access.
Run this command to add Index My Site to Claude Code.
claude mcp add --transport http indexmysite https://indexmysite.app/mcpTell your agent when to submit pages
Paste this into AGENTS.md, CLAUDE.md, or your Cursor rules. Your agent then submits pages on every release without being asked.
AGENTS.md
## Indexing
After you publish a new public page, or make a significant update to one,
submit its URL with the indexmysite MCP server (submit_urls).
- Put every URL from the same release in one job and name it after the release.
- Skip pages that only had small edits, drafts, and anything behind a login.
- Leave fast and bing off unless I ask for them.
- Tell me the job ID and when the first Google check is due.What your agent can do
Your agent can do everything the web app does. Every reply says what happens next, so your agent can explain it to you.
submit_urls
Send up to 2000 URLs in one job. Redirects, noindex pages, and error pages are skipped before any credit is used.
get_job and list_jobs
Every URL with its status, from checking to indexed or refunded, plus a plain-English note on what happens next.
approve_urls and recheck_urls
Approve thin pages after you have seen the warning, or check skipped pages again once you have fixed them.
Projects and credits
Group jobs by site or client, read each project’s index rate, and check your balance before a big release.
Frequently asked questions
Any client that supports remote MCP servers, including Claude Code, Claude, Cursor, Codex, ChatGPT, OpenCode, and Amp. Pick your client above for the exact setup.
No. The first time your client connects, a browser window opens so you can sign in and approve access. You can revoke it any time from Settings, then Connections.
Your client decides when to ask before calling a tool, so check its settings if you want to approve every submission. The server tells agents to leave the paid Fast and Bing add-ons off unless you ask, and pages with thin content wait for your approval before they are sent.
New public pages and pages with meaningful changes: features, pricing, docs, changelogs, comparisons, and launch posts. Skip small edits. Google says repeated requests for the same page do not speed things up, and each new submission uses a credit.
The MCP server is free to connect. Each sent URL uses 1 credit ($0.20), and a page confirmed as not indexed after the final check gets its standard credit back.
We check every URL once after 24 hours. Your full report follows around day 5, with final checks around day 14. Ask your agent to check the job any time, or have it check back the next day.
Agents with a terminal can use the indexmysite CLI, and any script can call the API with a key. Both do everything the MCP server does.
Do I need an API key?
No. The first time your client connects, a browser window opens so you can sign in and approve access. You can revoke it any time from Settings, then Connections.
Can my agent spend credits without asking?
Your client decides when to ask before calling a tool, so check its settings if you want to approve every submission. The server tells agents to leave the paid Fast and Bing add-ons off unless you ask, and pages with thin content wait for your approval before they are sent.
What should my agent submit?
New public pages and pages with meaningful changes: features, pricing, docs, changelogs, comparisons, and launch posts. Skip small edits. Google says repeated requests for the same page do not speed things up, and each new submission uses a credit.
What does it cost?
The MCP server is free to connect. Each sent URL uses 1 credit ($0.20), and a page confirmed as not indexed after the final check gets its standard credit back.
When will my agent know if a page is indexed?
We check every URL once after 24 hours. Your full report follows around day 5, with final checks around day 14. Ask your agent to check the job any time, or have it check back the next day.
My agent cannot use MCP. What else is there?
Agents with a terminal can use the indexmysite CLI, and any script can call the API with a key. Both do everything the MCP server does.
Connect your agent and index your next release
Create an account, buy credits from $25, and connect your client in a few minutes.