GrowSurf MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

growsurf_get_integration_connect_link

Read-onlyIdempotent

Return a dashboard link for connecting a specific integration (e.g., Stripe, PayPal) in GrowSurf. Use when a user wants to set up an integration, providing them the URL to open.

Instructions

Return a dashboard link that opens a specific integration's connect panel in the GrowSurf Program Editor (Options > Integrations). Use this whenever a user says they want to connect an integration, for example "connect Stripe", "set up PayPal or Wise payouts", "send Tango Card gift cards", or "sync signups to Mailchimp": call it with the integration key and give the user the returned url to open. Connecting an integration happens in the dashboard, not through the API. GrowSurf cannot link a Stripe, PayPal, Wise, or other account on the user's behalf, so hand them the link. integration must be one of the supported keys (some are camelCase, e.g. constantContact, helpScout). The link points at GROWSURF_CAMPAIGN_ID; pass campaignId to target a different program. The program is checked before the link is returned, and the result also reports whether the integration is already connected, enabled, or autoDisabled, so you can skip handing over a link the user does not need. If that check cannot run, programVerified comes back false and you still get a working production link. Tango Card, Tremendous, and Bask Health apply to referral programs only. Wise applies to affiliate programs only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`campaignId`	No	Target program for the link. Defaults to GROWSURF_CAMPAIGN_ID.
`integration`	Yes	The integration to connect. Must exactly match one of the supported keys (for example `wisecom`; some are camelCase, e.g. `constantContact`, `campaignMonitor`, `helpScout`, `pabblyConnect`, `baskHealth`).

Output Schema

TableJSON Schema

Name	Required	Description
`url`	No	Dashboard link that opens the integration's connect panel.
`note`	No	Instructions to relay to the user.
`label`	No	Human-readable integration name.
`enabled`	No	Whether the integration is switched on and currently working. Present only when `programVerified` is `true`.
`category`	No	The integration's category.
`connected`	No	Whether the program has stored credentials for this integration. Present only when `programVerified` is `true`.
`integration`	No	The integration key that was requested.
`autoDisabled`	No	Whether GrowSurf switched the integration off after repeated delivery failures. Present only when `programVerified` is `true`.
`referralOnly`	No	`true` when the integration applies to referral programs only.
`affiliateOnly`	No	`true` when the integration applies to affiliate programs only.
`programVerified`	No	`true` when the program's live integration list was read, so the program id is confirmed and the three state fields below are present and current. `false` when that read was unavailable, for example without an API key or `program:read`: the link still works but points at the production dashboard, and the state fields are omitted because the state is unknown. Never treat an absent state field as `false`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.14.0Sep 10, 2026

changedInput schema / properties / integration / enum

Previous value: -[
-  "stripe",
-  "chargebee",
-  "recurly",
-  "paypal",
-  "wisecom",
-  "tangocard",
-  "hubspot",
-  "salesforce",
-  "marketo",
-  "mailchimp",
-  "activecampaign",
-  "bentonow",
-  "mailerlite",
-  "resenddotcom",
-  "loopsdotso",
-  "convertkit",
-  "constantContact",
-  "campaignMonitor",
-  "aweber",
-  "klaviyo",
-  "mailjet",
-  "sendgrid",
-  "sendinblue",
-  "emailoctopus",
-  "customerio",
-  "getresponse",
-  "drip",
-  "googleanalytics",
-  "segmentanalytics",
-  "posthoganalytics",
-  "mixpanelanalytics",
-  "pendo",
-  "fullstory",
-  "heapanalytics",
-  "amplitude",
-  "googleads",
-  "metaads",
-  "linkedinads",
-  "twitterads",
-  "slack",
-  "intercom",
-  "helpScout",
-  "zapier",
-  "integromat",
-  "pabblyConnect",
-  "webhook",
-  "baskHealth"
-]New value: +[
+  "stripe",
+  "chargebee",
+  "recurly",
+  "paypal",
+  "wisecom",
+  "tangoCard",
+  "tremendous",
+  "hubspot",
+  "salesforce",
+  "marketo",
+  "mailchimp",
+  "activecampaign",
+  "braze",
+  "bentonow",
+  "mailerlite",
+  "resenddotcom",
+  "loopsdotso",
+  "convertkit",
+  "constantContact",
+  "campaignMonitor",
+  "aweber",
+  "klaviyo",
+  "mailjet",
+  "sendgrid",
+  "sendinblue",
+  "emailoctopus",
+  "customerio",
+  "getresponse",
+  "drip",
+  "googleanalytics",
+  "segmentanalytics",
+  "posthoganalytics",
+  "mixpanelanalytics",
+  "pendo",
+  "fullstory",
+  "heapanalytics",
+  "amplitude",
+  "googleads",
+  "metaads",
+  "linkedinads",
+  "twitterads",
+  "slack",
+  "intercom",
+  "helpScout",
+  "zapier",
+  "integromat",
+  "pabblyConnect",
+  "webhook",
+  "baskHealth",
+  "tangocard"
+]

addedOutput schema / properties / autoDisabled

Added value: +{
+  "description": "Whether GrowSurf switched the integration off after repeated delivery failures. Present only when `programVerified` is `true`.",
+  "type": "boolean"
+}

addedOutput schema / properties / connected

Added value: +{
+  "description": "Whether the program has stored credentials for this integration. Present only when `programVerified` is `true`.",
+  "type": "boolean"
+}

addedOutput schema / properties / enabled

Added value: +{
+  "description": "Whether the integration is switched on and currently working. Present only when `programVerified` is `true`.",
+  "type": "boolean"
+}

addedOutput schema / properties / programVerified

Added value: +{
+  "description": "`true` when the program's live integration list was read, so the program id is confirmed and the three state fields below are present and current. `false` when that read was unavailable, for example without an API key or `program:read`: the link still works but points at the production dashboard, and the state fields are omitted because the state is unknown. Never treat an absent state field as `false`.",
+  "type": "boolean"
+}

First observedv0.12.2Aug 25, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Even with readOnlyHint and idempotentHint already provided in annotations, the description adds valuable behavioral clarity: the program is checked before returning the link, the response reports connected/enabled/autoDisabled state, and a working link still comes back when programVerified is false. It also clearly states the product limitation that GrowSurf cannot link accounts on the user's behalf.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and every major sentence carries useful behavior or usage guidance. It is somewhat dense with examples and fallback behavior details, but nothing is filler. It could be slightly trimmed, especially around the examples, without losing necessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-health-parameter, read-only, non-destructive tool with an output schema, this description is effectively complete. It covers the main use intent, exactly what to give the user, integration restrictions, program targeting, state reporting, and fallback behavior. An agent should not need to guess anything else before calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already describes both parameters at 100% coverage, so the baseline is 3. The description adds value beyond the schema by explaining how to use the returned URL in conversation, emphasizing that integration must match a supported key, and adding constraints like referral-program-only integrations and Wise being affiliate-only.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a very specific verb and resource: 'Return a dashboard link that opens a specific integration's connect panel in the GrowSurf Program Editor.' It also gives concrete user-phrase examples and makes clear this is a link-returning tool, not a listing or mutation tool, so it is distinguishable from its siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to use it 'whenever a user says they want to connect an integration' and gives real examples like 'connect Stripe' and 'set up PayPal or Wise payouts'. It also clarifies that GrowSurf cannot connect accounts on the user's behalf. However, it does not explicitly route to an adjacent sibling like growsurf_list_integrations or growsurf_integration_guide for neighboring cases, so it stops just short of full when/when-not alternative guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server