tremendous-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TREMENDOUS_ENV | No | `sandbox` (testflight.tremendous.com) or `production` (api.tremendous.com). | sandbox |
| TREMENDOUS_SCOPES | No | OAuth scopes. | default |
| TREMENDOUS_CLIENT_ID | Yes | Tremendous OAuth app client ID. | |
| TREMENDOUS_TOKEN_DIR | No | Folder for the token files. | ~/.config/tremendous-mcp |
| TREMENDOUS_REDIRECT_URI | No | Must be the same as the redirect URI of the app. | https://localhost:8787/callback |
| TREMENDOUS_CLIENT_SECRET | Yes | Tremendous OAuth app client secret. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Tremendous rewards (SANDBOX: fake money). To send rewards: call review_rewards first so the user sees the draft, then send_rewards with the same draft_id. To see who received rewards: list_rewards. Orders in PENDING APPROVAL can be approved with approve_order.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_accountA | Show the connected Tremendous organization, the environment (SANDBOX or PRODUCTION) and the funding sources with their balances. Call this first to know which account you act on. |
| list_funding_sourcesA | List the funding sources (balance, card, bank, invoice) that can pay for rewards. Balances in this list can be a little stale. |
| list_productsA | List the reward products (gift cards, PayPal, Visa, charity, ...) in the catalog. Filter by country/currency and by a name search. Use product IDs in send_rewards.products. |
| list_campaignsA | List Tremendous campaigns (reward templates with products, message and branding). Use a campaign_id in send_rewards. |
| get_campaignB | Get one campaign with its products and email settings. |
| list_ordersA | List orders, newest first. Filter by creation date range, campaign, external_id, or status (for example PENDING APPROVAL to find orders that wait for approval). |
| get_orderB | Get one order with its status, payment and rewards. |
| get_rewardB | Get one reward: recipient, value, delivery method and delivery status. |
| list_rewardsA | Find which people received rewards. Filter by recipient email or name (substring), date range, campaign and delivery status. Returns one summary per recipient (count and total) and the reward rows, and shows an interactive table. Tremendous cannot filter by recipient, so this scans up to max_scan rewards (newest first); if |
| review_rewardsA | Prepare a batch of rewards WITHOUT sending anything. Checks the recipients, amounts, campaign/products and funding source, and shows an editable review form with a Send button. Use this before send_rewards. Returns a draft_id to pass to send_rewards. |
| send_rewardsA | SEND rewards: this spends money and emails/texts the recipients. It cannot be undone once a reward is redeemed. Creates one Tremendous order per recipient. Prefer calling review_rewards first and let the user confirm. draft_id makes retries safe: with the same draft_id, a recipient who was already paid is not paid again (even if you remove, reorder or add other recipients), so after a partial failure retry with the same draft_id. |
| resend_rewardA | Resend a reward email/SMS. Tremendous only allows this after a delivery failure (delivery_status FAILED). Optionally correct the email (EMAIL rewards) or the phone (PHONE rewards), not both. |
| cancel_rewardA | Cancel a reward and refund its value. Tremendous only allows this for rewards that are not redeemed and not expired (typically after a delivery failure). |
| generate_reward_linkA | Create a new redemption link for a LINK-delivery reward (other rewards return 403). WARNING: anyone with this link can redeem the reward. Share it only with the recipient. |
| approve_orderA | Approve an order in status PENDING APPROVAL so Tremendous executes it and sends the reward(s). Needs "Allow approvals via API" in Tremendous Team settings → Order approvals, otherwise Tremendous answers 403. Use list_orders with status "PENDING APPROVAL" to find them. |
| reject_orderA | Reject an order in status PENDING APPROVAL; its rewards are not sent. Needs "Allow approvals via API" in Tremendous Team settings → Order approvals, otherwise Tremendous answers 403. Use list_orders with status "PENDING APPROVAL" to find them. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Rewards dashboard | Who received rewards: totals, filters and per-reward actions |
| Send rewards | Editable review of a reward batch with a Send button |
TDQS
Scored across 16 tools
Nearly every tool targets a distinct resource plus action (approve vs reject, cancel vs resend vs generate link, review vs send). Minor overlap: get_account already surfaces funding sources with balances, which overlaps list_funding_sources, and list_rewards vs get_reward / list_orders vs get_order are close pairs but distinguished by summary vs single-record and the scan/truncation behavior is well documented.
All names are snake_case with a predictable verb_noun shape (list_*, get_*, approve_order, send_rewards), so an agent can pattern-match easily. Minor deviation is plurality: the reward-sending tools are plural (send_rewards, review_rewards) while other reward tools are singular (get_reward, cancel_reward, resend_reward), but the pattern is still readable.
16 tools is slightly above the typical 3-15 sweet spot but every tool maps to a genuine Tremendous operation (orders, rewards, campaigns, products, funding, account) without gratuitous duplication. The review/send split earns its extra tool by preventing accidental spend.
The surface covers the full reward lifecycle end-to-end: discover products/campaigns, review, send, retry, resend, regenerate links, cancel, plus order approval/rejection and account/funding context. Gaps are minor: campaigns are read-only (no create/update), and there is no dedicated order-creation or reward-detail search beyond list/get, but agents can work around these.