Connecting Odds MCP for VS Code + GitHub Copilot
AI coding & IDE tools · Last verified August 2026
VS Code supports MCP servers for Copilot agent mode, including remote HTTP servers with authentication.
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
- Supported
- Prompts
- Supported
Connecting Odds compatibility
Connecting Odds runs one MCP server for every client. VS Code + 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. VS Code + 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
Use the MCP: Add Server command in VS Code, choose an HTTP server, paste the Connecting Odds MCP URL and complete the sign-in prompt. Then enable the tools in Copilot agent mode.
Client interfaces change often, so follow VS Code + GitHub Copilot’s current MCP or custom connector setup flow and paste the URL above when it asks for a server address.
VS Code + GitHub Copilot MCP documentationExample query
Find remote React/TypeScript jobs posted in the last 7 days.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
If tools are missing, check the MCP server output panel and confirm agent mode is enabled.
- 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