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.
Analytics tools your agents can call
Showing 9 of 102 · Clear filters
Google Analytics
12 actionsREST APIProvider REST API
Query GA4 properties, reports, audiences, and events.
Amplitude
9 actionsREST APIProvider REST API
Query Amplitude event segmentation, funnels, retention, active users and annotations.
Google Search Console
8 actionsREST APIProvider REST API
Query search traffic, inspect how Google indexed a URL, and manage sitemaps.
Metabase
11 actionsREST APIProvider REST API
Browse saved questions, dashboards and database metadata, run a saved card, and query a database.
Microsoft Clarity
3 actionsMCP · sandboxedSandboxed MCP server
Read session recordings, dashboard analytics, and behaviour insights for a Clarity project.
Microsoft Clarity Sessions
2 actionsREST APIProvider REST API
Read individual Clarity session recordings and uncapped dashboard aggregates for one project, with full control over the window and the page size.
Mixpanel
9 actionsREST APIProvider REST API
Run Mixpanel segmentation, funnel and retention queries, and browse events, properties and cohorts.
PostHog
12 actionsREST APIProvider REST API
Run HogQL queries and read insights, events, flags, cohorts and recordings.
Segment
10 actionsREST APIProvider REST API
Inspect a Segment workspace: sources, destinations, tracking plans, warehouses, and functions.
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.