Integrations
Connect Search Console to Gemini CLI
Register AutoPSEO in the Gemini CLI settings file and the model reads your Search Console data without you leaving the terminal.
Add the server
Gemini CLI reads MCP servers from its settings file. Add an entry under mcpServers named autopseo, set the HTTP URL to https://app.autopseo.com/mcp, and add an Authorization header carrying your bearer key. A per-project settings file overrides the one in your home directory, which is convenient when different repositories map to different properties.
Confirm it attached
Run the /mcp command in a session. A healthy connection lists the server as connected along with its 19 tools; a missing header shows up as an auth failure rather than an empty list.
- Start with "list my Search Console properties" to check the account
- A 401 means the key is malformed, unknown or revoked
- A 429 means you are over the per-minute limit, not that the key is wrong
Where it earns its place
The terminal is where the content change actually happens, so the useful pattern is asking for the current performance of a URL before editing it and the rank changes for its queries a fortnight after shipping.
Keys and hygiene
Use a read-only key for anything interactive. Reference it through an environment variable so the settings file stays safe to commit, and revoke keys individually when a machine changes hands.
Ready to see what your Search Console data is hiding?
Connect a property and every report fills in immediately. No credit card needed.