In one paragraph
ConnectorBay publishes 2214 connectors with 18859 tools across 1,000+ services. Every connector is a remote MCP server (Model Context Protocol, streamable HTTP) with a matching REST API described by OpenAPI 3.1 and an OpenAI function-calling tool list. 1494 of them are bring your own key (BYOK) connectors: the agent sends the user's own API key in the X-Upstream-Key header and ConnectorBay forwards it to the vendor for that one call only. The rest need no key. Connectors are read-only by default; device connectors can change a device's state only after the user confirms that exact change.
How a connector works
Each connector runs on its own host, https://<slug>.connectorbay.com, and exposes the same tools three ways: /mcp for MCP clients, POST /v1/tools/<tool> for REST, and /openai/<slug>.json on this site for OpenAI-style function calling. A hosted OpenAI-compatible endpoint, https://connectorbay.com/v1/chat/completions, runs the tool loop for any model you bring. The full catalog is machine-readable at /.well-known/mcp.json and /llms.txt.
What we promise
- Keys and tool inputs are used for the one call and never stored, logged, cached or echoed.
- A BYOK key goes only to the vendor hosts the connector declares, over HTTPS, without following redirects.
- Nothing pays, posts, sends messages or deletes. Device actions need an explicit
confirm = yes. - When a source fails, the agent gets a structured error, not a guess.
- ConnectorBay is independent: it is not affiliated with or endorsed by any AI assistant provider or any of the services its connectors reach.
Who it is for
People who use Claude, ChatGPT, Cursor, Windsurf, VS Code agents, Gemini-based agents or their own agent framework and want it to read from the tools they already pay for, without writing an integration. And developers who want one catalog of MCP servers with consistent error handling, rate limits and privacy rules.
Contact
Write to agent@connectorbay.com for a missing connector, a wrong fact, a partnership or press.