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.

7 functions 7 read 0 write Manual OAuth token auth

Submit Google Search Console feedback View package source

Google Search Console for agents

Credentials can be configured manually in web or CLI hosts.

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-search-console
package: google-search-console
auth_strategy: oauth2_manual_token Manual OAuth token
cli_setup_supported: true
cli_runtime_supported: true
mcp_gateway_supported: true
lua_supported: true
supports_multi_account: true

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.gsc_list_sites`	Read `read`	2	List all sites the authenticated user has access to in Google Search Console. Returns site URLs and permission levels.
`google-search-console.gsc_get_site`	Read `read`	1	Get details for a specific site in Google Search Console, including permission level.
`google-search-console.gsc_list_sitemaps`	Read `read`	4	List sitemaps submitted for a site in Google Search Console. Returns sitemap URLs, types, and indexing status.
`google-search-console.gsc_get_sitemap`	Read `read`	2	Get details for a specific sitemap in Google Search Console, including indexing status and any errors.
`google-search-console.gsc_list_search_analytics`	Read `read`	5	Query search performance data from Google Search Console — clicks, impressions, CTR, and average position. Group by dimensions like query, page, country, or device.
`google-search-console.gsc_list_url_inspection`	Read `read`	4	Inspect URLs for a site in Google Search Console. Returns indexing status, crawl information, and any detected issues.
`google-search-console.gsc_get_current_user`	Read `read`	0	Get the authenticated user's profile from Google Search Console. Returns email and account information.