Add GSC PAP to OpenAI Codex CLI

Steps

1. 1

   Install Codex CLI

   If you have not already, install Codex CLI from openai.com or via the package manager for your platform. Sign in with `codex login` using your OpenAI account. Verify with `codex --version` (>= 0.30).

2. 2

   Sign in to GSC PAP and copy your token

   Visit gscpap.com and click "Sign in with Google." Grant the read-only Search Console + GA4 scopes. After the OAuth callback, the connect page shows a one-time bearer token, copy it now.

3. 3

   Edit ~/.codex/config.toml

   Open the Codex config file. Add an `[mcp_servers.gsc-pap]` block with the URL and a reference to an env var for the bearer token. The env-var pattern keeps the secret out of your dotfiles.

   tomlCopy

   [mcp_servers.gsc-pap]
   url = "https://mcp.gscpap.com/mcp"
   bearer_token_env_var = "GSC_PAP_TOKEN"

4. 4

   Export the token and restart Codex

   Add `GSC_PAP_TOKEN=<paste-here>` to your shell rc file (`~/.zshrc` / `~/.bashrc`) so it persists across sessions. Source the rc, then run `codex` and ask: "What sites are in my Search Console?" Codex calls list_sites and replies with your verified properties.

   shellCopy

   echo 'export GSC_PAP_TOKEN="paste-your-token-here"' >> ~/.zshrc
   source ~/.zshrc
   codex

Common gotchas

• ·Codex resolves the env var at process start. If you exported it in one terminal but launched Codex in another, the var is missing. Either re-source your rc or use a terminal multiplexer that inherits env.
• ·If `codex mcp list` doesn't show gsc-pap, run `codex mcp add` interactive flow to verify the URL is reachable. The most common cause is a typo in the TOML (missing closing quote, etc.).
• ·Codex IDE extension (the VS Code variant) reads the same `~/.codex/config.toml`. Edit once, available in both surfaces.
• ·Token expired or 401: mint a new bearer at /account/tokens. Old tokens stay valid until you revoke them, so you can rotate without breaking other clients.