@referalli/mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REFERALLI_API_KEY | Yes | Required. A Referalli API key. Create one in Referalli under Settings → API keys. The key's scopes decide what the server can do: a read-only key gives a read-only assistant. | |
| REFERALLI_API_URL | No | API base URL. Default `https://referalli.com`; use `http://localhost:4000` for a local API. | https://referalli.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_programsB | List the affiliate programs in this organization |
| program_overviewB | Funnel and revenue overview for the last 30 days |
| partner_performanceC | Per-partner clicks, referrals, revenue, and commissions |
| list_referralsB | Recent referrals with attribution channel and status |
| list_fraud_casesB | Open fraud cases awaiting review |
| roi_summaryA | Credit ROI: what the credit you granted (referee rewards, commission credit) cost and what it earned back. Amounts are integer minor units (cents) in the reporting currency unless |
| roi_traceA | The timeline behind a credit ROI figure for ONE customer (customerRef) or ONE partner (partnerId); pass exactly one. It lists grants, credit used, and the cash payments after, so you can explain why a number is what it is. Cash is real money paid; credit is not. Profit fields are null when no margin is set. |
| roi_patternsA | Customers or partners matching a named credit-ROI pattern: credit_only (used credit, never paid cash), churn_at_exhaustion (stopped paying once credit ran out), bonus_collector (partner collected credit without paying themselves), negative_partner (a partner whose referrals lose money overall). Only subjects whose evidence window has fully elapsed are listed, so a young customer is never flagged. Each entry has a subject and detail amounts in minor units. |
| my_referral_linkA | A partner's own referral link, for answering a partner in chat or an AI agent. Pass the partner's verified id in your system (partnerExternalRef); never guess it from an email. |
| my_balanceA | A partner's own commission balance: pending (in its hold period), approved (due in the next payout) and paid, in integer minor units of |
| my_next_payoutA | When a partner's next payout run is (YYYY-MM-DD, or null when none is scheduled) and how much approved commission it would include. |
| create_partnerA | Create a partner. Write: the first call returns a preview and a confirmToken; call again with confirm: true and that token to do it. |
| create_linkA | Create a tracked link for a partner in a program. Write: the first call returns a preview and a confirmToken; call again with confirm: true and that token to do it. |
| create_couponA | Create a coupon code that attributes to a partner. Write: the first call returns a preview and a confirmToken; call again with confirm: true and that token to do it. |
| approve_referralA | Approve a referral held for review. Write: the first call returns a preview and a confirmToken; call again with confirm: true and that token to do it. |
| void_referralA | Void a referral. Permanent: future payments earn nothing. Write: the first call returns a preview and a confirmToken; call again with confirm: true and that token to do it. |
| pause_referralA | Pause a referral: its payments are recorded but earn nothing until resumed. Write: the first call returns a preview and a confirmToken; call again with confirm: true and that token to do it. |
| resume_referralA | Resume a paused referral. Write: the first call returns a preview and a confirmToken; call again with confirm: true and that token to do it. |
| approve_due_commissionsA | Approve every commission line whose hold period has passed. Write: the first call returns a preview and a confirmToken; call again with confirm: true and that token to do it. |
| create_payout_runA | Create a payout run (a draft: it is not executed, no money moves). Write: the first call returns a preview and a confirmToken; call again with confirm: true and that token to do it. |
| settle_commissionA | Mark a commission line paid because you credited the partner yourself (store credit). Write: the first call returns a preview and a confirmToken; call again with confirm: true and that token to do it. |
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 21 tools
Most tools have clearly distinct resource+action targets: referral state changes (approve/void/pause/resume) are mutually exclusive, and the my_* self-service tools are clearly scoped to the calling partner. The only real overlap is in the reporting cluster (program_overview vs partner_performance vs roi_summary vs roi_patterns vs roi_trace), but the descriptions draw useful lines between funnel overview, per-partner metrics, aggregate ROI, cohort patterns, and single-subject trace.
Everything is consistently snake_case, and the write tools follow a predictable verb_noun pattern (create_coupon, approve_referral, create_payout_run). Minor deviation: several reporting tools are noun-first without a verb (program_overview, partner_performance, roi_summary, roi_patterns, roi_trace), and the my_* namespace is a third convention, but all remain readable and unambiguous.
At 21 tools this sits in the heavy band for a single affiliate/referral domain. Each tool does earn its place (the ten write tools each cover a distinct lifecycle transition with a uniform confirm-token flow), but the surface is large enough that an agent must scan a lot of options to pick correctly.
Core flows are covered: partner/link/coupon creation, referral state machine, commission approval and settlement, payout run creation, and rich ROI reporting. Notable gaps: there is no list_partners or get_partner despite create_partner and partner-scoped reports, no way to list commissions or inspect/cancel a payout run after creation, no list_coupons, and list_fraud_cases has no matching resolve/dismiss tool — a dead end.