Connecting Odds
All AI clients

Connecting Odds MCP for Gemini CLI

Agent & developer clients · Last verified August 2026

Supported

Google's open-source terminal agent supports HTTP and stdio MCP servers.

MCP compatibility

Verified: this client can connect to a remote MCP server like Connecting Odds.

MCP support
Supported
Remote MCP
Supported
OAuth
Partial
Tools
Supported
Resources
Partial
Prompts
Partial

Connecting Odds compatibility

Connecting Odds runs one MCP server for every client. Gemini CLI calls the same search_jobs and get_job tools, backed by the same ranked search engine the website uses — there is no client-specific search behaviour.

Required transport

Remote MCP (Streamable HTTP). The endpoint is:

https://connectingodds.com/mcp

Authentication

OAuth 2.1 with dynamic client registration. Gemini CLI redirects you to Connecting Odds, you approve the connection, and the client stores a scoped access token. You never paste a key, password or database credential.

Setup steps

Add Connecting Odds to your Gemini CLI settings as an httpUrl MCP server, then run /mcp to confirm.

For a terminal client, the install is one command:

claude mcp add --scope user --transport http connecting-odds 'https://connectingodds.com/mcp'
Gemini CLI MCP documentation

Example query

Find remote machine learning jobs.

Expected result

Example response — illustrative, not real listings:

Found 18 matching Connecting Odds jobs.

1. Senior Python Engineer
   Company: Example Company
   Location: Remote — US
   Salary: $150K–$180K
   Skills: Python, AWS, PostgreSQL
   Visa: Sponsorship available
   View job: https://connectingodds.com/jobs/…

2. Staff Backend Engineer
   Company: Example Company Two
   Location: Austin, TX (Hybrid)
   Salary: not stated by the employer
   Skills: Python, Django, Kubernetes
   View job: https://connectingodds.com/jobs/…

Troubleshooting

Run /mcp list to inspect the server state and any auth prompt.

  • MCP connection failed: Remove the connector and add it again with the copied URL, then restart the client.
  • Authentication failed: Disconnect and reconnect to trigger a fresh sign-in, and approve the Connecting Odds consent screen.
  • Tools not appearing: Refresh the connector's tools, then start a new chat or session.
  • No jobs returned: Loosen one constraint at a time — drop the salary floor or widen the location — and ask again.
Full troubleshooting guide

Only public job data is returned, and account-scoped tools act as your signed-in user.

Developer documentation