Manage GrowSurf referral and affiliate programs, participants, rewards, tracking, webhooks, and analytics through MCP-compatible assistants.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent ā or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag ā we're steadily working through the catalog.
š” Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by GrowSurf.
growsurf_bulk_delete_participantsCheck each row outcome. `analyticsErasure.status: "pending"` means analytics erasure is still pending; do not repeat successful rows.
GrowSurf MCP server exposes GrowSurf referral and affiliate program operations to MCP-compatible AI clients. It can help create programs, configure rewards, manage participants, record referral or affiliate activity, and inspect campaign analytics. It also provides guided implementation material for tracking, signup flows, qualifying actions, webhooks, widgets, native mobile SDKs, and GrowSurf Window integrations.
The server supports both operational API calls and static guidance. Static resources and integration snippets can be used without credentials, while protected business actions require authorization. Available code examples cover TypeScript, Python, PHP, Ruby, and Java.
The GrowSurf MCP server can run locally as a Node.js stdio process or remotely through GrowSurf's hosted endpoint. Local execution uses the npm package command, while compatible clients can connect to https://mcp.growsurf.com using OAuth when they support remote Streamable HTTP.
For campaign-scoped operations, the client can use a default campaign ID, provide a campaignId argument, or first list available campaigns. Team-level actions do not require a campaign ID. The server wraps common GrowSurf REST workflows and publishes MCP safety hints for read-only, destructive, idempotent, and open-world operations.
Node.js 22 or newer is required. A local or manually configured remote connection uses GROWSURF_API_KEY; GROWSURF_CAMPAIGN_ID can provide the default program for campaign-specific calls. A scoped API key is acceptable if it grants access to the intended tools and programs.
Run the local server with:
Hosted OAuth is available for clients that support remote connections. An account can also be created through the account-creation tool after the authorized owner approves the action and accepts GrowSurf's terms and privacy policy. The resulting API key must be stored securely, and owner email verification is required before protected calls.
The GrowSurf MCP server supports these workflow areas:
Guided prompts can advise on program design, troubleshooting, starter content, reward setup, tracking, embedding, and webhook wiring. The repository also includes an installable agent skill bundle.
Campaign-scoped tools need a campaign ID, unless the operation is team-level or the tool is given one directly. Static guidance does not require credentials, but API-backed actions generally do. Account creation is an exception and requires explicit owner approval; unverified accounts are removed after seven days.
API-key rotation is not exposed as an MCP tool. Rotate keys in GrowSurf Settings or through a direct REST or SDK client. For bulk participant deletion, inspect each row result: an analyticsErasure.status value of pending means erasure is still in progress, and successful rows should not be submitted again.
Factual signals from GitHub, npm, and our automated checks ā not a rating.
No reviews yet ā be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/growsurf)<a href="https://allmcps.com/mcp/growsurf"><img src="https://allmcps.com/api/badge/growsurf?style=directory" alt="GrowSurf on AllMCPs" /></a>