GrowSurf MCP server

Hosted server

Point a compatible MCP client at the hosted endpoint:

https://mcp.growsurf.com

The client completes OAuth while you sign in to GrowSurf, pick a team, and approve the requested scopes. Your assistant never handles an API key. The connection acts only on the team you selected, and API-key rotation is deliberately not available through MCP.

Discovery metadata

• OAuth Protected Resource Metadata — RFC 9728
• OAuth Authorization Server Metadata — RFC 8414

Local server and CLI

The same tools run locally over stdio from the official npm package, which also provides the GrowSurf CLI:

npx -y @growsurfteam/growsurf-mcp

Set GROWSURF_API_KEY in the client configuration. Optionally set GROWSURF_CAMPAIGN_ID to default program-scoped tools to one program; it is not a credential, and an explicit campaignId argument overrides it.

Read the CLI guide for commands, or the growsurf-mcp source on GitHub.

No account yet

An assistant whose user has no GrowSurf account can connect with no credentials and call growsurf_create_account:

https://mcp.growsurf.com/onboard

The account owner then verifies their email address before the key unlocks.

Public read-only endpoint

GrowSurf also publishes a credential-free Streamable HTTP endpoint for public resources at growsurf.com/.well-known/mcp, described by its MCP server card. Use it to read GrowSurf's first-party agent and developer index without signing in.

Before you connect

A credential proves permission, not intent. Confirm with the account owner before anything destructive or irreversible.

See auth.md for the full credential-handling rules, and Build with AI for the customer-facing overview.