Connecting Odds MCP for GitHub Copilot
AI coding & IDE tools · Last verified August 2026
Copilot agent surfaces consume MCP servers configured in the host editor or on github.com.
MCP compatibility
Verified: this client can connect to a remote MCP server like Connecting Odds.
- MCP support
- Supported
- Remote MCP
- Supported
- OAuth
- Supported
- Tools
- Supported
- Resources
- Partial
- Prompts
- Not verified
Connecting Odds compatibility
Connecting Odds runs one MCP server for every client. GitHub Copilot 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/mcpAuthentication
OAuth 2.1 with dynamic client registration. GitHub Copilot 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
Configure Connecting Odds as an MCP server in your Copilot host (VS Code, JetBrains or github.com) following GitHub's current MCP documentation.
Client interfaces change often, so follow GitHub Copilot’s current MCP or custom connector setup flow and paste the URL above when it asks for a server address.
GitHub Copilot MCP documentationExample query
Find software engineering jobs above $150K.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
Copilot must be in agent mode for MCP tools to appear.
- 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.
Only public job data is returned, and account-scoped tools act as your signed-in user.
Developer documentation