
Searchdock Cli
io.github.xplormityaiv0.1.3Updated Oct 11, 2026
Read-only Google Search Console analytics, URL inspection and sitemaps via SearchDock CLI.
Overview
Read-only Google Search Console access for an assistant: search analytics, URL inspection, and sitemap status.
- What it does
- Exposes five read-only MCP tools — searchdock_sites, searchdock_analytics, searchdock_sitemaps, searchdock_inspect, and searchdock_report — over a local stdio server. Analytics covers clicks, impressions, CTR, average position, and breakdowns by query, page, date, device, or country, with optional brand-query filtering. Sitemaps reports Google's processing status, and inspect returns Google's indexed version of a specific URL. Reports can be combined for chosen URLs and written to a new JSON file.
- When to use it
- Useful when an assistant should answer questions about a site's Google Search performance, check whether specific URLs are indexed, or watch sitemap processing without opening the Search Console UI. It is a reporting and inspection tool, not a full technical SEO audit, and it cannot request indexing or test live URLs.
- Requirements
- Runs locally as a stdio process; Node.js 22 or later is required for every distribution, including the Python launcher. Google access needs your own Google Cloud project with the Search Console API enabled and a Desktop app OAuth client JSON, plus a one-time browser consent. No shared developer credentials are included and no environment variables are declared.
Installation
In SourceWeft
- Open Searchdock Cli in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
SearchDock CLI — Google Search Console CLI
Read Google Search Console analytics, inspect indexed URLs, and monitor sitemaps from your terminal or AI agent.
SearchDock is open source, runs locally, and requests read-only Google access. Use the same core through npm, Python, MCP, a Codex or Claude Code plugin, or a standalone agent skill. Bing Webmaster Tools support is planned.
Set up with your agent
Copy this prompt into your coding agent:
Installation commands
Node.js 22 or later is required for every distribution.
The Python package is a launcher containing the exact same JavaScript runtime. It has no separate Google implementation. If you install both packages, use python -m searchdock_cli to select the Python launcher explicitly.
Install both skills for Codex in the current project:
Replace codex with claude-code, cursor, opencode, or your supported agent. Add --global only for installation across projects. Skills do not install the CLI or authorize Google access. Plugin, MCP and manual setup.
To run from source:
Connect Google Search Console
Create a Google OAuth Desktop app client in your own Google Cloud project, enable the Search Console API, and download the client JSON. See Google setup for the steps and testing-mode limits. No shared developer credentials are included.
Google opens a local browser consent flow. SearchDock uses PKCE, validates the callback state, and listens only on 127.0.0.1. It requests webmasters.readonly and keeps the refresh token in your operating system's per-user configuration directory, outside this repository. Credentials are stored as permission-protected local JSON, not encrypted by SearchDock. See privacy.
Commands
--json writes machine-readable results to stdout and errors to stderr with a nonzero exit status. --output saves JSON to a new file and refuses to overwrite an existing one. Keep private reports out of Git yourself. CSV is not yet supported. For URLs containing commas, use the MCP urls array or the JavaScript API for batch inspection.
Report windows default to 28 days ending three days before today in Pacific Time, to allow for Search Console processing. You can specify exact dates. Finalized data may still lag. Pagination supports up to 100,000 requested rows, but Google's API returns top rows and omits some anonymized query data. Missing rows do not prove zero demand; zero impressions make average position meaningless.
AI agents and MCP
SearchDock provides five read-only MCP tools: searchdock_sites, searchdock_analytics, searchdock_sitemaps, searchdock_inspect, and searchdock_report. Authenticate locally first; MCP tools do not start consent or change account settings.
Add this stdio server to any compatible MCP client:
For a source checkout, set command to node and args to ["/absolute/path/searchdock-cli/dist/cli.cjs", "mcp"]. Windows clients that launch npx.cmd through a shell may need command: "cmd" and args: ["/c", "npx", "--yes", "[email protected]", "mcp"]. Use your client's Windows configuration guidance.
Plugins use the same pinned npm version:
In Claude Code:
This one-step command requires Claude Code 2.1.275+. Earlier versions can use /plugin marketplace add xplormityai/searchdock-cli, then /plugin install searchdock@searchdock --scope project.
For standalone skills, copy both skills/searchdock and skills/searchdock-setup into your agent's skills directory. Codex uses ~/.agents/skills/; Claude Code uses ~/.claude/skills/. Install the CLI separately. Both skills are included in the plugin. The repository includes portable Agent Plugins, Codex and Claude manifests; local stdio plugins are not automatically listed in hosted plugin directories.
You can also install the skill with the open skills installer:
SearchDock is published in the official MCP Registry under io.github.xplormityai/searchdock-cli. Release workflows update its metadata using GitHub OIDC.
What the Google API can and cannot tell you
SearchDock's report flags returned sitemap errors/warnings, pending processing and non-PASS verdicts for the URLs you inspect. It is not a complete technical SEO audit, and it does not provide invented SEO/AEO/GEO scores.
JavaScript API
The provider registry declares capabilities separately. Bing can be added as an adapter without changing the CLI, MCP or Python distribution model. Provider-specific differences must remain explicit. See architecture.
Develop and release
Release instructions cover npm/PyPI accounts, OIDC trusted publishing, versioning and GitHub release artifacts. Package creation alone does not publish anything.
Built by Xplormity Collective. MIT license.
Source: README.md at commit d091292
Tools
0Version history
1- v0.1.3LatestOct 11, 2026

