Every app an agent can reach
169 maintained connectors across 20 categories, 2,144 named actions between them. Give your hosted agents the toolkits they need in a project, or connect an external agent through one MCP endpoint. The project policy applies to both.
AI tools reached as mcp servers
Showing 0 of 169 · Clear filters
Nothing matches that combination yet.
Every category holds at least one connector, but not every category holds one of each connection type.
Show all 169Four ways a connector reaches its provider
The catalog is not one adapter with 169 config files. A connector talks to whatever its provider actually ships. Calling any of them is free; where the call runs decides whether it holds a sandbox you then pay for by the second.
- Remote MCP server5 connectors · bills nothing
- The provider runs a streamable HTTP MCP server. The gateway calls it directly and forwards nothing else.
- Sandboxed MCP server4 connectors · bills sandbox time
- A stdio MCP server is started inside the project sandbox, spoken to over its standard streams, and torn down.
- Provider REST API154 connectors · bills nothing
- Each action is pinned to one named HTTP endpoint declared in the connector, signed with your stored credential at the moment of the call.
- Sandboxed CLI6 connectors · bills sandbox time
- The vendor's own command line tool runs inside the project sandbox, with secrets passed through the environment rather than the argument list.
Choose what each agent can call
Install a connector, decide who may call which of its actions, and read back the exact request and response for every call an agent made.