GrowSurf MCP Server

Official

by growsurf

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Get Integration Connect Link

growsurf_get_integration_connect_link

Read-onlyIdempotent

Get a GrowSurf dashboard link to an integration's connect panel so users can complete account setup when the API cannot connect it for them.

Instructions

Return a dashboard link to an integration's connect panel in the GrowSurf Program Editor (Options > Integrations). Connecting Stripe, PayPal, Wise, or another account requires the user to complete the dashboard flow; the API cannot connect an account on their behalf. integration accepts supported keys, including camelCase keys such as constantContact and helpScout. The result reports whether the integration is connected, enabled, or autoDisabled. If the program check cannot run, programVerified is false and the result still includes a production dashboard link. Tango Card, Tremendous, and Bask Health apply only to referral programs. Wise applies only to affiliate programs. Targets campaignId if supplied, otherwise GROWSURF_CAMPAIGN_ID.

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?

Annotations already cover read-only/idempotent safety, yet the description adds substantial behavioral detail: the dashboard-completion requirement, the connected/enabled/autoDisabled result fields, the programVerified=false fallback that still returns a production link, and program-type applicability rules. This is rich context beyond structured data.

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?

Dense prose that front-loads the purpose and the API-cannot-connect caveat. Every sentence carries useful information, though the program-type and result-field details are somewhat packed together rather than scannable.

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-parameter read tool this is fully covered: connection semantics, edge cases (programVerified false), result flags, and program-type caveats are all addressed, and an output schema exists so return structure need not be re-explained.

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?

With 100% schema coverage the baseline is 3, but the description adds genuine meaning beyond the schema: camelCase key examples, the program-type restrictions (Tango Card, Tremendous, Bask Health referral-only; Wise affiliate-only), and the campaignId fallback behavior. It does not add syntax or validation detail beyond the schema.

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?

States a specific verb and resource: return a dashboard link to an integration's connect panel in the GrowSurf Program Editor. It also clarifies the critical constraint that the API cannot connect accounts itself, distinguishing this tool from connect/action tools and from growsurf_list_integrations.

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?

Gives clear context for use: the user must complete the dashboard flow, so this tool is the hand-off point. However, it does not explicitly name sibling alternatives (e.g. growsurf_list_integrations or growsurf_integration_guide) or state when not to use it.

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

Deploy Server