Connect Supermetrics to Goose
Give Goose governed access to Supermetrics’s 15 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Supermetrics to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Add Supermetrics to Runlayer
Supermetrics isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Goose to Runlayer
Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches Supermetrics’s 15 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to Supermetrics
Sign in the way Supermetrics requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Supermetrics from Goose
Supermetrics’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
15 Supermetrics tools in Goose
Runlayer policy decides which of these Goose users can call.
Accounts discovery
Discover connected accounts for a data source.
Campaign and resource get
Get campaigns or related resources.
Contact Supermetrics
Send feedback, create a support ticket (only when the user authorizes it), or submit a sales enquiry.
Creative picker
Open the creative picker to browse, upload, AI-generate, or import ad creatives with visual preview.
Data query
Query data from Google Ads, Facebook Ads, Google Analytics, LinkedIn Ads, TikTok Ads, Microsoft Ads, Shopify, HubSpot, and 200+ other platforms.
Data source discovery
Discover data sources or get a source's configuration.
Field discovery
Discover available fields (metrics and dimensions) for a data source.
Get async query results
Retrieve results from a data_query using its schedule_id.
Control
What Runlayer can see and stop in Goose
Some controls apply to every client at the gateway. Others depend on what Goose exposes to Runlayer.
Gateway policy (available)
Every Supermetrics call from Goose passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Goose as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before Goose runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Goose’s model sees it.
Redact output in place (not available)
Goose cannot apply masking, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.
Frequently asked questions
Connect more
