---
title: "Connect an agent to gscdump"
description: "Set up the packaged agent skill or MCP server and check one Search Console result."
canonical_url: "https://gscdump.com/gscdump-cli/guides/start/connect-an-agent"
last_updated: "2026-10-03T07:15:31.530Z"
---

# Connect an agent to gscdump

Agents can use the packaged skill to run CLI commands. An MCP client can call live Google tools. The MCP server reads live Google data, not your local Store, and does not expose Bing tools.

## Choose a connection

::table{tabindex="0"}
| Connection  | Use it for                                     | First command                         |
| ----------- | ---------------------------------------------- | ------------------------------------- |
| Agent skill | CLI commands, Store queries, Bing, and Reports | `gscdump skill install --agent codex` |
| MCP server  | Live Google requests through a stdio client    | `gscdump mcp`                         |
::

Check the [commands reference](/gscdump-cli/api/commands) for CLI setup. Authenticate first with [Choose access](/gscdump-cli/guides/start/choose-access).

## Set it up

::pre{tabindex="0"}
```bash
gscdump skill install --agent codex
gscdump auth status --json
gscdump sites --json
```
::

Use `--agent claude` for Claude Code or `--agent codex` for Codex. For another client that reads agent skills, pass `--target /path/to/skills`. The CLI writes a `gscdump/` directory there. Have the agent read the installed `SKILL.md` before its first gscdump task. You can also [read the raw SKILL.md](/SKILL.md) or [view the skill on skilld](https://skilld.dev/gh/harlan-zw/gscdump).

The skill runs CLI commands with your selected authentication and local Store access. It instructs agents to ask before Site, sitemap, indexing, or Store deletion changes. It may send a sanitized CLI papercut report for each distinct problem, unless you forbid reporting. See [the skill text](/SKILL.md) for its reporting rules.

For MCP, configure your client's stdio server command as `gscdump mcp`. Pass the same profile and environment credentials to that process. The server can list tools before authentication, but Google calls then return an access error.

## Ask for one Site and Report

Ask: “List my Search Console Sites. Run the movers Report for [example.com](http://example.com) for two complete weeks. Show the dates, source, changed pages, and uncertainty.” Review the returned Site and date window before acting. MCP exposes `list-reports` and `run-report`; its live Report set includes `brand`, `movers`, `opportunities`, `pre-publish`, and `risks`. The [Reports reference](/gscdump-cli/api/reports) describes their inputs.

## If the agent cannot read data

Check `gscdump auth status --json` and `gscdump sites --json` in the same profile. Restart an MCP client after changing its environment credentials. If it requests `growth`, `health`, or `triage` through MCP, use the CLI with a Store instead. If a live fetch reaches its row budget, describe the result as partial.

## Try an investigation

Use the [weekly traffic review](/gscdump-cli/guides/investigate-traffic/weekly-triage) to check the Report against rows. More setup: [Start](/gscdump-cli/guides/start).

## Sitemap

See the full [sitemap](/sitemap.md) for all pages.