Connect Gemini CLI

Last updated from API version 2026-10-06 at 2026-10-25 22:49 UTC (live spec, refreshed hourly). openapi.json

Gemini CLI connects to the Owlbound MCP server over HTTP and signs in with your Owlbound account in the browser. No client ID, secret or API key is needed.

1. Add the server#

Add Owlbound to your Gemini CLI settings: ~/.gemini/settings.json for all projects, or .gemini/settings.json in one project.

{
  "mcpServers": {
    "owlbound": {
      "httpUrl": "https://app.owlbound.ai/api/v1/mcp"
    }
  }
}

Use httpUrl (streamable HTTP), not url: that one means SSE, which Owlbound does not serve.

2. Sign in#

1. Start Gemini CLI with gemini.
2. Run /mcp auth owlbound.
3. Your browser opens Owlbound: sign in, pick the workspace, review the access and click Allow.
4. Back in the terminal, run /mcp to see the Owlbound tools.

Gemini CLI keeps the tokens in ~/.gemini/mcp-oauth-tokens.json and refreshes them on its own. Run /mcp auth owlbound again if you are asked to sign in.

Optional: limit what it may ask for#

{
  "mcpServers": {
    "owlbound": {
      "httpUrl": "https://app.owlbound.ai/api/v1/mcp",
      "oauth": {
        "enabled": true,
        "scopes": ["read"]
      }
    }
  }
}

Scopes are read, enrich, write and act. You can also untick scopes on the Owlbound consent screen.

With an API key instead#

For CI and scripts, send a v1 API key as a header:

{
  "mcpServers": {
    "owlbound": {
      "httpUrl": "https://app.owlbound.ai/api/v1/mcp",
      "headers": { "Authorization": "Bearer $OWLBOUND_API_KEY" }
    }
  }
}

Create the key in Settings > Settings > Workspace > Developerand keep it out of version control. The key's scopes and daily caps limit what Gemini CLI can do.

What Gemini CLI can and cannot do#

• Gemini CLI acts as you, in the workspace you picked, with at most your role's rights and the scopes you allowed.
• Every action tool runs a dry run first, so you see the plan, the targets and the credits before anything runs.
• Sends (LinkedIn, email, CRM) are never sent by Gemini CLI. They wait for a person in Approvals in the Owlbound app, and Gemini CLI gives you the link. See how actions work.

Disconnect#

In Owlbound, open Settings > Connected apps and click Disconnect. To remove it from the CLI, delete the owlbound entry from settings.json.

Troubleshooting#

• “This redirect URI is not allowed”: set no redirectUri in the oauth block. The Gemini CLI default, http://localhost:<port>/oauth/callback, is accepted.
• 405 Method Not Allowed: the server is set up with url (SSE). Use httpUrl.