GrowSurf MCP + REST API

Run GrowSurf from Claude Code, Cursor, or Codex.

Connect GrowSurf's MCP server to the tools your team already uses. Ask for a referral program, rewards, install checks, or analytics, then review each change before launch.

Built for reviewable setup work Hosted MCP·REST API·OpenAPI-backed·Program analytics
How agents use GrowSurf

A launch workflow your team can inspect

The agent is not guessing from a scraped page. It uses GrowSurf's MCP server, API, docs, and account context to do the real setup work in a way your team can review.

Built for the way growth teams actually launch referral programs. Keep strategy in plain language, keep execution inside GrowSurf, and keep the handoff to engineering explicit.
Marketing & ops

Describe the launch. Let the agent assemble the Program.

Give the agent the offer, audience, reward logic, and launch constraints. It can turn that into a GrowSurf Program and bring back the pieces your team should approve.

  • Create a referral or affiliate program from a plain-language brief
  • Configure single- or double-sided rewards, cash, credit, or gift cards
  • Review Design, Emails, Options, Installation, and Rewards before launch
  • Add, update, and manage participants without hunting through menus
  • Pull program and participant analytics when someone asks for status
312%Average customer ROI
7.4MParticipants tracked
$355MReferral revenue
Developers

Use the same context inside the codebase.

When the work moves from Program setup to app integration, the agent can guide implementation with GrowSurf's official docs and snippets.

Install pathsUniversal snippet, JavaScript SDK, native iOS, native Android, and embeddable elements.
Backend wiringWebhooks, participant auto-auth, HMAC checks, and server-side participant updates.
REST snippetsOfficial examples for TypeScript, Python, PHP, Ruby, and Java.
Connect in a minute

Connect GrowSurf to your MCP client

Use hosted OAuth in ChatGPT, Claude, Cursor, Codex, and other compatible remote MCP clients, or run the local stdio server with npx.

MCP server URL
https://mcp.growsurf.com/mcp

In ChatGPT: open Settings → Security and login and turn on Developer mode. Managed workspaces may require an admin to enable it. Open Settings → Plugins, select +, and create a developer-mode app named GrowSurf with a short description and the URL above. Approve access, then start a new chat and select + → More → GrowSurf.

MCP server URL
https://mcp.growsurf.com

In Claude: open Customize → Connectors, select +, then Add custom connector. Name it GrowSurf and use the URL above. Select Add, then Connect, and sign in. In a conversation, use + → Connectors to enable GrowSurf. On Team or Enterprise, an organization owner adds it first under Organization settings → Connectors.

terminal
# Hosted OAuth, no API key paste
claude mcp add --transport http --scope user growsurf https://mcp.growsurf.com
claude mcp login growsurf

# Local stdio fallback
claude mcp add growsurf \
  -e GROWSURF_API_KEY=your_api_key \
  -e GROWSURF_CAMPAIGN_ID=your_campaign_id \
  -- npx -y @growsurfteam/growsurf-mcp

On first use, Claude Code opens GrowSurf sign-in and consent. See the Build with AI guide.

~/.cursor/mcp.json
{
  "mcpServers": {
    "growsurf": {
      "type": "http",
      "url": "https://mcp.growsurf.com"
    }
  }
}

In Cursor: open or create ~/.cursor/mcp.json, add the growsurf server shown above, and enable it. Complete sign-in when Cursor requests authorization. The guide also includes API-key and local stdio fallbacks.

terminal
# Hosted OAuth, no API key paste
codex mcp add growsurf --url https://mcp.growsurf.com
codex mcp login growsurf

# Local stdio fallback
codex mcp add growsurf \
  --env GROWSURF_API_KEY=your_api_key \
  --env GROWSURF_CAMPAIGN_ID=your_campaign_id \
  -- npx -y @growsurfteam/growsurf-mcp

You can also add url = "https://mcp.growsurf.com" under [mcp_servers.growsurf] in ~/.codex/config.toml.

mcp_config.json
{
  "mcpServers": {
    "growsurf": {
      "serverUrl": "https://mcp.growsurf.com"
    }
  }
}

In Antigravity: open MCP Servers → Manage MCP Servers → View raw config, then paste the config above. Save it, open Settings → Customizations, and select Authenticate for GrowSurf. The guide also includes API-key and local stdio fallbacks.

MCP server URL
https://mcp.growsurf.com

Claude connectors are tied to your Claude account. In Customize → Connectors, select +, add a custom connector named GrowSurf with the URL above, and select Connect. In a conversation, use + → Connectors to enable GrowSurf. On Team or Enterprise, an organization owner must add it first. Prefer a local server? Use the stdio config from the Build with AI guide.

terminal
code --add-mcp '{"name":"growsurf","type":"http","url":"https://mcp.growsurf.com"}'

Or open the Command Palette, run MCP: Add Server, and choose HTTP. Open Copilot Chat and confirm that GrowSurf appears in the available tools. Use a GrowSurf tool, then approve sign-in when VS Code prompts you.

terminal
gemini mcp add --transport http growsurf https://mcp.growsurf.com

Run /mcp auth growsurf in Gemini CLI and approve access in your browser. Then run /mcp to check the connection.

mcp_config.json
{
  "mcpServers": {
    "growsurf": {
      "serverUrl": "https://mcp.growsurf.com"
    }
  }
}

In Devin Desktop (formerly Windsurf): open the MCPs panel, or go to Devin Settings → Cascade → MCP Servers, and open the raw config. Add the server above, refresh the list, then sign in and approve access.

MCP server URL
https://mcp.growsurf.com

In Cline: open the MCP Servers panel, choose Remote Servers, add GrowSurf with the URL above, connect, then sign in and approve access.

remote or local MCP client
# Remote Streamable HTTP with OAuth
https://mcp.growsurf.com

# API-key remote fallback
https://mcp.growsurf.com/mcp
Authorization: Bearer your_api_key

# Local stdio fallback
npx -y @growsurfteam/growsurf-mcp

Use the hosted OAuth URL when your MCP client supports remote Streamable HTTP and OAuth. Use the API-key or local stdio fallback when it does not.

Hosted OAuth uses your GrowSurf sign-in Local fallback requires Node.js 22+ API-key fallback still supports manual MCP clients
Where things stand

Hosted OAuth and local MCP today

Use hosted OAuth when your client supports it, or keep the local/API-key paths for clients that need them.

Available now

Hosted OAuth MCP

Claude Code, Codex, Cursor, Antigravity, and compatible remote MCP clients can connect at https://mcp.growsurf.com. GrowSurf handles sign-in and consent, so you do not paste an API key into the agent.

Available now

Local MCP server (stdio)

The open-source @growsurfteam/growsurf-mcp package runs locally in Claude Code, Cursor, Codex, Claude Desktop, Antigravity, and other MCP clients.

Available now

Manual API-key fallback

If your MCP client does not support GrowSurf sign-in, use https://mcp.growsurf.com/mcp and add Authorization: Bearer YOUR_API_KEY.

What agents can do

A full program, driven by prompts

Every tool is a safe wrapper over the same GrowSurf REST API that powers the dashboard.

Create programs

Spin up referral or affiliate programs with type-appropriate defaults, clone them, and manage their lifecycle.

Configure rewards

Set single- or double-sided rewards — cash, account credit, gift cards — and update them any time.

Manage participants

Add and update participants, email them, trigger referral credit, and pull their activity and analytics.

Read analytics

Fetch program totals, time-series, status counts, and conversion rates to report on performance.

Review settings

Ask the agent to fetch Design, Emails, Options, Installation, and Rewards before launch.

Wire webhooks & installs

Create and test webhooks, generate install snippets, and get official SDK code in five languages.

FAQ

Build with AI, answered

Can an AI agent really create and run a GrowSurf referral program?
Yes. GrowSurf publishes an open-source Model Context Protocol (MCP) server that wraps the GrowSurf REST API. Once you connect it to an AI agent, the agent can create a referral or affiliate program, configure rewards, add and manage participants, and read analytics, all in plain language and backed by the same REST API the dashboard uses.
Which AI tools and MCP clients does GrowSurf support?
GrowSurf's hosted MCP endpoint works over Streamable HTTP with OAuth for Claude Code, Codex, Cursor, Antigravity, and compatible remote MCP clients. The MCP server also runs locally over stdio for Claude Code, Cursor, Codex, Claude Desktop, Antigravity, and other local MCP clients.
Is there a hosted or remote MCP connector?
Yes. Connect supported remote MCP clients at https://mcp.growsurf.com. GrowSurf opens sign-in and consent, so you do not need to paste an API key. If your client does not support sign-in, use the API-key setup in the Build with AI guide.
Do I need a GrowSurf API key to use the MCP server?
Not when your client supports GrowSurf sign-in. Claude Code, Codex, Cursor, Antigravity, and compatible remote clients connect with your GrowSurf account. Local setups and clients without sign-in support may still ask for a GrowSurf API key. Static guidance and code-snippet tools run without credentials.
What can the agent do for developers embedding GrowSurf into an app?
For developers, the agent gives guided installation of the universal code snippet, the JavaScript SDK, native iOS and Android SDKs, embeddable elements, webhooks, and participant auto-auth, plus official REST API library snippets for TypeScript, Python, PHP, Ruby, and Java.

Trusted by marketing and product teams at fast-growing companies across B2C, SaaS, fintech, AI, healthtech, education, and insurance