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.
Security tools your agents can call
Showing 8 of 102 · Clear filters
1Password
8 actionsREST APIProvider REST API
Inventory the vaults and items a 1Password Connect server can reach, without reading any secret value.
Bitwarden
26 actionsREST APIProvider REST API
Manage an organisation's members, groups, collections, and policies.
HashiCorp Vault
11 actionsREST APIProvider REST API
Map a Vault cluster - its secret engines, secret paths, policies, auth methods and health - without reading any secret value.
Infisical
10 actionsREST APIProvider REST API
Read, add, and rotate the secrets in a project's environments.
Microsoft Entra ID
12 actionsREST APIProvider REST API
Read a tenant's users, groups, applications, directory roles, devices and sign-in logs through Microsoft Graph.
Okta
12 actionsREST APIProvider REST API
Read an Okta org's users, groups, applications, MFA enrolment and system log.
Snyk
9 actionsREST APIProvider REST API
Read organizations, projects, targets, security issues, SBOMs, and scan settings.
- V
Vanta
10 actionsREST APIProvider REST API
Read compliance tests, controls, policies, evidence documents, frameworks, vendors, people, and monitored devices.
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.