Autousers

Gemini CLI

schedule3 mincalendar_todayLast updated 2026-04-30

Add Autousers to Google's Gemini CLI via native HTTP OAuth or Bearer token.

infoGemini CLI ≥ v0.40 supports remote MCP servers natively. Run all gemini mcp commands in your regular terminal, not inside the gemini chat prompt.

Option 1 — OAuth (recommended)

Register the server. Gemini CLI auto-discovers the OAuth endpoints from the Autousers MCP server on first connection.

gemini mcp add --transport http autousers https://mcp.autousers.ai/mcp

Register Autousers MCP server

Open Gemini CLI and trigger the OAuth flow. A browser window opens for sign-in; tokens are cached at ~/.gemini/mcp-oauth-tokens.json and refreshed automatically.

gemini
> /mcp auth autousers

Run inside the gemini chat prompt

warningDo not use the mcp-remote stdio shim with Gemini CLI — its OAuth handshake currently fails against the Autousers server. Use the native HTTP transport above.

Option 2 — Bearer token (headless / CI)

Generate an API key at /settings/api-keys, export it, then register the server with a static Authorization header.

export AUTOUSERS_API_KEY=ak_live_...
gemini mcp add --transport http \
  --header "Authorization: Bearer $AUTOUSERS_API_KEY" \
  autousers https://mcp.autousers.ai/mcp

Register with API key (no browser required)

Verify

gemini mcp list

Expect: autousers: https://mcp.autousers.ai/mcp (http) - Connected

Then open gemini and run /mcp — you should see autousers listed with all 39 tools. Try "list my evaluations" to confirm an authenticated tool call works end-to-end.

Re-authenticate or remove

# Re-run OAuth (e.g. after revoking access)
gemini mcp auth autousers

# Remove the server entirely
gemini mcp remove autousers

Manage the connection

infoBy default gemini mcp add writes to project-scoped settings (./.gemini/settings.json). Pass --scope user to write to ~/.gemini/settings.json so the connection follows you across projects.
Was this article helpful?