GrowSurf MCP Server

Official

by growsurf

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Get Program Installation

growsurf_get_campaign_installation

Read-onlyIdempotent

Retrieve the installation and tracking configuration for your GrowSurf program, returning all fields and current values. Target a specific campaign ID if needed, otherwise the default is used.

Instructions

Fetch the Installation tab configuration for your GrowSurf program (embed/installation and tracking setup). Returns the full object with every field and its current value — the same shape you send back on update. Targets campaignId if you pass it, otherwise GROWSURF_CAMPAIGN_ID.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`campaignId`	No	Target program (campaign) id for this call. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Pass the `id` returned by growsurf_create_campaign to configure or operate a program you just created, without restarting the server.

Output Schema

TableJSON Schema

Name	Required	Description
`mobile`	No	GrowSurf iOS and Android SDK settings.
`signup`	No	Custom signup-form settings (used with `FORM_DETECTION`).
`shareUrl`	No	The landing page referred friends reach from a referral link. Set this before adding other origins to `allowedUrls`.
`allowedUrls`	No	Every additional browser origin where the GrowSurf Window or SDK may run, including development origins such as `http://localhost:3000`. Preserve the full array when patching it. An origin absent from both `shareUrl` and this list can return `403`.
`signupEvent`	No	The signup tracking method: automatic form detection, or participants added via the SDKs and REST API.
`referralTrigger`	No	Referral programs only. `ON_SIGNUP` counts a referral as soon as the friend signs up; `CUSTOM` also requires a qualifying action.
`useGrowSurfHostedLinks`	No	Use GrowSurf-hosted referral links that route clicks by the visitor's device. Mainly for mobile apps.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.12.2Aug 25, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, and non-destructive behavior. The description adds useful context beyond that: it returns the full object in the exact shape used for update and describes the default campaignId behavior (GROWSURF_CAMPAIGN_ID). No contradiction with annotations.

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

Conciseness5/5

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

Three short, purposeful sentences: what it fetches, what it returns and how that relates to updates, and the parameter targeting default. Every sentence earns its place, and the most important information is front-loaded.

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

Completeness4/5

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

For a simple, read-only getter with one optional parameter and an output schema, nothing important is missing: the resource, response shape, and default behavior are all covered. An agent can invoke it correctly without guessing.

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

Parameters3/5

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

Schema coverage is 100% for the only parameter. The description repeats the defaulting behavior already stated in the schema and adds little extra semantic meaning. This sits at the baseline for full schema coverage.

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

Purpose4/5

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

Uses the specific verb 'Fetch' with a clearly defined scope: the Installation tab configuration (embed/installation and tracking setup). This sets it apart from sibling getters like growsurf_get_campaign_design or growsurf_get_campaign_emails, though it doesn't explicitly name them.

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?

Makes the context clear: call this when you need the Installation tab configuration for a GrowSurf program. The phrase 'same shape you send back on update' naturally links it to update_campaign_installation. It doesn't explicitly list exclusions, but the purpose is clear enough for the agent to choose this over sibling getters.

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

Deploy Server