Connecting Odds MCP for Microsoft Copilot

Works, but with caveats — capability varies by version, plan, platform or transport.

MCP support

◐Partial

Remote MCP

◐Partial

OAuth

◐Partial

Tools

●Supported

Resources

?Not verified

Prompts

?Not verified

Connecting Odds runs one MCP server for every client. Microsoft 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.

Remote MCP (Streamable HTTP). The endpoint is:

OAuth 2.1 with dynamic client registration. Microsoft 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.

Use Copilot Studio to add Connecting Odds as an MCP server for your agent, following Microsoft's current MCP documentation.

Client interfaces change often, so follow Microsoft Copilot’s current MCP or custom connector setup flow and paste the URL above when it asks for a server address.

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/…

Consumer Copilot chat may not expose MCP; use Copilot Studio agents instead.

• 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.