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.
Communication tools reached as rest apis
Showing 7 of 102 · Clear filters
Slack
11 actionsREST APIProvider REST API
Search conversations and send messages to your workspace.
Discord
12 actionsREST APIProvider REST API
Read and post in a Discord server's channels, and look up its members, roles and threads.
Microsoft Teams
11 actionsREST APIProvider REST API
Read Teams channels and chats, follow threads, and post messages and replies.
Resend
11 actionsREST APIProvider REST API
Send transactional email and manage domains, contacts and broadcasts.
SendGrid
10 actionsREST APIProvider REST API
Send email, and read deliverability stats, suppressions, templates and contacts.
Twilio
9 actionsREST APIProvider REST API
Send SMS, read message and call logs, and look up phone numbers.
Zoom
10 actionsREST APIProvider REST API
Schedule and manage Zoom meetings, and read recordings, participants and users.
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.