GrowSurf MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Create Mobile Participant Token

growsurf_create_mobile_participant_token

Create or fetch a GrowSurf participant and generate a participant-scoped mobile SDK token for trusted direct affiliate enrollment, bypassing public application review.

Instructions

Create or fetch a participant, then create a participant-scoped mobile SDK token via GrowSurf REST. Participant creation is trusted direct enrollment and bypasses the public application review flow for affiliates. Targets campaignId if you pass it, otherwise GROWSURF_CAMPAIGN_ID.

Input Schema

TableJSON Schema

Name	Required	Description
`email`	Yes
`lastName`	No
`metadata`	No
`firstName`	No
`ipAddress`	No
`campaignId`	No	Target program (campaign) id for this call. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Program IDs also identify newly created programs without restarting the server.
`referredBy`	No
`fingerprint`	No
`isAffiliate`	No	Sets whether the participant is an affiliate. Use `true` only for trusted direct enrollment. Public applicants should follow the program's configured application flow.
`referralStatus`	No
`mobileInstanceId`	No

Output Schema

TableJSON Schema

Name	Required	Description
`isNew`	No	Whether this request created a new participant.
`expiresIn`	No	Token lifetime in seconds.
`participant`	No	The participant record (same shape as the `growsurf_get_participant` result).
`participantToken`	No	Participant-scoped bearer token for GrowSurf mobile SDK participant endpoints.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.19.9Oct 3, 2026

changedInput schema / properties / campaignId / description

Previous value: -"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."New value: +"Target program (campaign) id for this call. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Program IDs also identify newly created programs without restarting the server."

First observedv0.12.2Aug 25, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already establish the mutation profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), and the description adds genuinely useful context: participant creation bypasses the public application review flow for affiliates, and the campaign target falls back to an env var. It stops short of disclosing auth requirements, rate limits, or what 'create or fetch' means for repeat calls.

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?

Three tight, front-loaded sentences with no filler. The core action comes first and the enrollment/targeting caveats follow, which is appropriate sizing for the information present.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the enrollment semantics are covered. However, for an 11-parameter mutation tool with 18% schema coverage, the description should have compensated for the many undocumented fields; instead it leaves that gap open.

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

Parameters2/5

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

Schema coverage is only ~18% — just campaignId and isAffiliate are described. The description adds only the campaignId fallback behavior, leaving 9 of 11 parameters (email, firstName, lastName, metadata, ipAddress, referredBy, fingerprint, referralStatus, mobileInstanceId) undocumented in both schema and description.

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?

The description names a specific verb+resource (create a participant-scoped mobile SDK token) and clarifies the two-step behavior (create-or-fetch participant, then tokenize). It is clearly specific, but it never differentiates this tool from close siblings like growsurf_add_participant or growsurf_mobile_sdk_guide.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the 'trusted direct enrollment' framing and the campaignId/`GROWSURF_CAMPAIGN_ID` targeting note, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative for the non-mobile participant case.

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

Deploy Server