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.
Infrastructure tools reached as rest apis
Showing 9 of 102 · Clear filters
Cloudflare
12 actionsREST APIProvider REST API
Manage zones, DNS records, Workers, and analytics.
Coolify
16 actionsREST APIProvider REST API
Manage applications, services, deployments, and servers.
Hetzner
12 actionsREST APIProvider REST API
Manage cloud servers, networks, volumes, and firewalls.
DigitalOcean
12 actionsREST APIProvider REST API
Inspect droplets, managed databases, App Platform apps, Kubernetes clusters, load balancers, and billing.
Google Cloud
12 actionsREST APIProvider REST API
Inspect projects, Compute Engine, Cloud Storage, Cloud Run, Cloud SQL and Cloud Logging.
HCP Terraform
11 actionsREST APIProvider REST API
Read workspaces, runs, plans, state outputs, variables, and projects.
Kubernetes
12 actionsREST APIProvider REST API
Inspect pods, deployments, nodes and events on a cluster, and read pod logs.
Microsoft Azure
12 actionsREST APIProvider REST API
Inventory Azure subscriptions and resources, inspect virtual machines, and read the activity log.
Vercel
11 actionsREST APIProvider REST API
Inspect projects, deployments, domains, and build logs.
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.