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.
Productivity tools your agents can call
Showing 8 of 102 · Clear filters
Box
11 actionsREST APIProvider REST API
Browse folders, search content, read file and folder details, create folders, delete, share links, and see who has access.
Dropbox
12 actionsREST APIProvider REST API
Browse folders, search files, read metadata, create folders, move, copy, delete, and share links.
Gmail
10 actionsREST APIProvider REST API
Read mail, search threads, apply labels, draft, send, and delete.
Google Calendar
8 actionsREST APIProvider REST API
Read calendars, check availability, and create, update, or cancel events.
Google Drive
16 actionsREST APIProvider REST API
Find, read and organise files, create folders and documents, and manage who can see them.
Google Sheets
11 actionsREST APIProvider REST API
Read and write spreadsheet ranges, append rows, add sheets, and create new spreadsheets.
Microsoft Outlook
12 actionsREST APIProvider REST API
Read and search Outlook mail, draft and send messages, and manage calendar events.
Ploxs
20 actionsMCP · remoteRemote MCP server
Create and edit designed Google Slides decks from content, HTML, or a brand style.
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.