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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/refgrow/refgrow-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server