Search Console
Search analytics, URL inspection, and sitemaps under control
Query search performance, inspect how Google sees a URL, and manage sites and sitemaps. The four writes — adding or removing sites and sitemaps — are exactly the kind of quiet, structural change the policy engine exists for.
$ claude mcp add --transport http search-console \
https://mcp.getducto.com/search-console
✓ connected — 11 tools
read-only until you set a policy
What your agent does here
Real Search Console work, in conversation
Pull search performance
Full search analytics queries by page, query, country, and device — the data behind every SEO decision.
gsc_search_analyticsgsc_list_sitesgsc_status
Inspect URLs like Google does
Index status, canonical, and crawl details for any URL on a verified property.
gsc_inspect_urlgsc_get_site
Manage sitemaps deliberately
Submit and remove sitemaps, with deletes flagged destructive and gateable behind approval.
gsc_submit_sitemapgsc_delete_sitemapgsc_list_sitemaps
Governed writes
How writes are enforced
Site and sitemap changes are previewed and audited like every other write. Deletions carry destructive annotations, so your policy can require a human sign-off before they run.
The full request path is on the security architecture page.
Tool reference
Every tool in the search-console mount
Generated from the running gateway's tool registry — this is the complete list, not a highlight reel.