Can I use Google Search Console as a CLI?

Yes. KosmoKrator exposes a Google Search Console CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Google Search Console through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Google Search Console tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Google Search Console credentials stored?

Google Search Console credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Google Search Console MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

analytics

Google Search Console MCP, CLI, and Lua Integration for AI Agents

Google Search Console integration docs for AI agents: MCP gateway setup, Google Search Console CLI commands, Lua API reference, credentials, and function schemas.

9 functions 5 read 4 write OAuth browser flow auth

Submit Google Search Console feedback View package source

Google Search Console for agents

OAuth can be configured in web hosts through redirect and in CLI hosts through local/device authorization; runtime works with stored tokens.

Use this integration from Lua code mode, the headless integrations CLI, or the KosmoKrator MCP gateway. The same package metadata powers all three surfaces.

Machine-Readable Metadata

integration_slug: google_search_console
route_slug: google/google-search-console
package: google
auth_strategy: oauth2_authorization_code OAuth browser flow
cli_setup_supported: true
cli_runtime_supported: true
mcp_gateway_supported: true
lua_supported: true
supports_multi_account: false

Quick Links

Lua APIAgent-facing namespace and function reference. Google Search Console CLIHeadless setup and direct function calls. Google Search Console MCPMCP gateway setup for external clients. Submit feedbackReport missing tools, auth problems, wrong docs, or runtime issues. ContributeAdd tools or improve metadata in the integrations repo.

Google Search Console MCP Client Matrix

Use these pages when a specific agent client or framework needs copy-pasteable MCP setup for Google Search Console.

Google Search Console CLI Matrix

Use these pages for direct Google Search Console CLI workflows in scripts, CI, cron, and agent wrappers.

CI Google Search Console CLI for CI. Cron Jobs Google Search Console CLI for cron jobs. Shell Scripts Google Search Console CLI for shell scripts. Headless Automation Google Search Console CLI for headless automation. Coding Agents Google Search Console CLI for coding agents.

Function Catalog

Function	Type	Parameters	Description
`google_search_console.google_search_console_add_site`	Write `write`	1	Add a new site property to Google Search Console.
`google_search_console.google_search_console_delete_site`	Write `write`	1	Remove a site property from Google Search Console.
`google_search_console.google_search_console_delete_sitemap`	Write `write`	2	Remove a sitemap from Google Search Console.
`google_search_console.google_search_console_get_sitemap`	Read `read`	2	Get details of a specific sitemap in Google Search Console. Returns the sitemap's path, last submitted/downloaded dates, whether it's a sitemap index, and content type breakdown with submitted vs indexed URL counts.
`google_search_console.google_search_console_inspect_url`	Read `read`	2	Check a URL's indexing status in Google Search Console. Returns: index verdict, coverage state, last crawl time, robots.txt state, indexing state, rich results, mobile usability, and AMP status.
`google_search_console.google_search_console_list_sitemaps`	Read `read`	1	List all submitted sitemaps for a Google Search Console property. Returns each sitemap's path, last submitted/downloaded dates, whether it's a sitemap index, and content type counts (submitted vs indexed URLs).
`google_search_console.google_search_console_list_sites`	Read `read`	0	List all verified Google Search Console sites/properties with their permission levels. Use this first to discover available properties before querying performance data or inspecting URLs. Returns each site's URL (e.g., "sc-domain:example.com" or "https://www.example.com/") and your permission level.
`google_search_console.google_search_console_performance`	Read `read`	10	Query Google Search Console search performance data (clicks, impressions, CTR, position). Common queries: "top pages by clicks" → dimensions=["page"]. "Top search queries" → dimensions=["query"]. "Traffic trend" → dimensions=["date"]. "Mobile vs desktop" → dimensions=["device"]. "Blog section" → dimensions=["page"], filters=[{dimension:"page", operator:"contains", value:"/blog/"}]. Combine dimensions: dimensions=["query","device"] for queries by device.
`google_search_console.google_search_console_submit_sitemap`	Write `write`	2	Submit a new sitemap to Google Search Console.