Connect Gemini CLI

Gemini CLI reads MCP servers from its settings file. Point it at your endpoint and give it an access token.

A token is read-only: Gemini CLI can read your posts, schedule, plan and AI token balance, but it cannot write or publish. If you want an assistant that writes, connect ChatGPT or Claude instead.

Set it up

Create an access token

On the MCP page, in the Access tokens card, click Create token, name it something like Gemini CLI on my laptop, and copy the token. It is shown only once — see Access tokens for the full walkthrough.

Copy the config

Scroll to Setup guide, select the Gemini CLI tab and copy the block under Add to ~/.gemini/settings.json. It already has your endpoint filled in:

{
  "mcpServers": {
    "avada-blog": {
      "type": "http",
      "url": "https://…/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  },
  "mcp": {
    "allowed": ["avada-blog"]
  }
}

Add it to your settings file

Open ~/.gemini/settings.json — create the file if it isn't there — and paste the block in. Replace YOUR_TOKEN with the token you created.

⚠️

Keep the mcp.allowed list. Without it Gemini CLI reports the server as connected but registers none of its tools, so the assistant answers from guesswork instead of your blog's data.

Check it worked

Restart Gemini CLI and run /mcp. avada-blog should be listed with its tools. Ask "how many posts does my blog have?" to confirm.

Replace the token

Edit the Authorization line in ~/.gemini/settings.json with the new token and restart Gemini CLI.

Disconnect

Remove the avada-blog entry from ~/.gemini/settings.json and restart Gemini CLI. Also revoke the token on the MCP page, otherwise it stays usable anywhere else you pasted it.

Trouble connecting? See Troubleshooting.

Cursor Codex CLI