102 integrations, ready to install
102 maintained connectors across 20 categories, 1143 named actions between them. Your agents reach all of it through one MCP endpoint, behind the policy you set.
Database tools reached as command line
Showing 3 of 102 · Clear filters
MySQL
8 actionsCLI · sandboxedSandboxed CLI
Inspect schema, tables, indexes and keys on a MySQL or MariaDB database.
PostgreSQL
12 actionsCLI · sandboxedSandboxed CLI
Inspect the schema of a PostgreSQL database.
Redis
11 actionsCLI · sandboxedSandboxed CLI
Inspect keys, values and server state on a Redis instance.
Four ways a connector reaches its provider
The catalog is not one adapter with 102 config files. A connector talks to whatever its provider actually ships, and where the call runs is what a call costs.
- Remote MCP server2 connectors · 1 credit per call
- The provider runs a streamable HTTP MCP server. The gateway calls it directly and forwards nothing else.
- Sandboxed MCP server3 connectors · 5 credits per call
- A stdio MCP server is started inside the project sandbox, spoken to over its standard streams, and torn down.
- Provider REST API92 connectors · 1 credit per call
- 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 CLI5 connectors · 5 credits per call
- 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.