Open plumbing, and what we’re building next.
Every connector is a hosted MCP server with a matching REST API. Here is how it fits together, and where we plan to take it for developers.
Available today
Two ways in, same tools.
Each connector runs on its own host with a hosted MCP endpoint and a matching REST API, generated from one tool registry so they never drift apart.
- MCP · streamable HTTP, stateless, spec 2025-06-18+, no auth
- REST ·
POST /v1/tools/<tool>, OpenAPI 3.1 at/openapi.json - Catalog · every endpoint and policy at /.well-known/mcp.json
- Health ·
/healthon every host; optional Bearer key raises rate limits
Three examples. Any connector works the same way: swap in its slug.
{
"mcpServers": {
"eli5": {
"type": "http",
"url": "https://eli5.connectorbay.com/mcp"
},
"plate": {
"type": "http",
"url": "https://plate.connectorbay.com/mcp"
},
"devkit": {
"type": "http",
"url": "https://devkit.connectorbay.com/mcp"
}
}
}curl -X POST https://eli5.connectorbay.com/v1/tools/decode_money_document \
-H 'Content-Type: application/json' \
-d '{"text": "Amount billed $1,240.00 Plan paid $980.00 You owe $260.00"}'curl https://connectorbay.com/.well-known/mcp.json
Under the hood
The same rules apply to every connector on ConnectorBay.
Hosted MCPOne endpoint per connector at
https://<slug>.connectorbay.com/mcp. Stateless, no sign-in, works with any MCP-capable agent.REST + OpenAPIEvery tool is also a JSON POST endpoint described by an OpenAPI 3.1 spec, generated from the same registry as the MCP tools.
Limits and healthA
/health check on every host. Free tier: 60 requests a minute and 300 a day per client. An optional Bearer key raises them.Read-only, nothing keptNo writes, no accounts, and tool inputs are never stored. When a source is down the agent gets a structured reason, not a guess.
In the labPlanned, not released
Developer tools
Next we want to build simple, single-purpose tools for developers: the kind you run from a terminal or call from a script, to make building on MCP and agent tooling faster. We are still shaping them, so none of this is released yet.
Ideas we’re exploring
- Command-line utilities. Quick tools you can run in a terminal or pipe into scripts.
- Inspection helpers. Try a connector’s tools and see the exact request and response.
- Starter kits. Minimal templates for shipping your own MCP server.
These are directions, not commitments. What would help you most?
Tell us what to buildReviewing ConnectorBay for a directory or platform?
Every connector has its own page, documentation, privacy policy, terms and support page, and the full catalog is machine-readable.