Refgrow MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REFGROW_API_KEY | Yes | Your Refgrow API key (starts with `rgk_`) | |
| REFGROW_API_URL | No | Base URL of your Refgrow instance | https://refgrow.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_affiliatesA | List all affiliates in your Refgrow project with their stats (clicks, signups, purchases, earnings). Supports filtering by status and pagination. |
| get_affiliate_detailsC | Get detailed information about a specific affiliate by their email address, including click count, signups, purchases, and earnings. |
| create_affiliateC | Create a new affiliate in your Refgrow project. An affiliate receives a unique referral code and can start referring customers. |
| update_affiliateC | Update an existing affiliate's details such as email, referral code, status, or partner slug. |
| delete_affiliateB | Delete an affiliate from your project. This also removes their associated referral data. |
| list_referralsB | List referred users (signups tracked through affiliate links). Filter by affiliate or conversion status. Shows which affiliate referred each user. |
| get_referral_detailsC | Get details for a specific referred user by their email address. |
| create_referralC | Manually create a referred user record, optionally linking them to a specific affiliate. |
| list_conversionsA | List conversions (signups and purchases) tracked in your affiliate program. Filter by type, affiliate, date range, or paid status. |
| get_conversionC | Get details for a specific conversion by its ID. |
| create_conversionB | Manually create a conversion (signup or purchase). For purchases, the commission is auto-calculated from project settings if value is not provided. You can identify the affiliate by ID or referral code. |
| update_conversionB | Update a conversion's details. Commonly used to mark a conversion as paid or update its value. |
| delete_conversionC | Delete a conversion record by its ID. |
| list_couponsB | List coupon codes associated with affiliates in your project. Filter by status, affiliate, or coupon code search. |
| get_couponC | Get details for a specific coupon by its ID. |
| create_couponB | Create a new coupon code linked to an affiliate. Optionally tie it to a Stripe coupon ID or LemonSqueezy discount code for automatic attribution. |
| update_couponC | Update an existing coupon's code, linked affiliate, payment provider IDs, or status. |
| delete_couponA | Delete a coupon by its ID. If linked to a Stripe coupon, it will also be deleted from Stripe. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Every tool has a clearly distinct purpose with no ambiguity. Each tool targets a specific resource (affiliate, conversion, coupon, referral) and action (create, delete, get, list, update), making it easy for an agent to select the correct one. For example, create_affiliate and update_affiliate are clearly differentiated by their actions on the same resource.
Tool names follow a highly consistent verb_noun pattern throughout, such as create_affiliate, list_conversions, and update_coupon. All tools use snake_case with clear verbs (create, delete, get, list, update) and nouns (affiliate, conversion, coupon, referral), making the set predictable and readable.
With 18 tools, the count is well-scoped for an affiliate management domain, covering CRUD operations for four core resources (affiliate, conversion, coupon, referral). Each tool earns its place by providing necessary functionality without redundancy, such as detailed get operations alongside list views.
The tool surface offers complete CRUD/lifecycle coverage for the affiliate management domain, with no obvious gaps. All four resources have create, get, list, update, and delete operations (except referrals, which lack update and delete, but this is reasonable as referrals are typically immutable records). This ensures agents can handle full workflows without dead ends.