tremendous-mcp
Related Servers
Alternatives to tremendous-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI clients to check an application balance and preview or send bulk SMS and airtime, either through a hosted OAuth connection that needs no local install or via a self-hosted stdio/Cloudflare Workers deployment using your own credentials. Sending is preview-only by default and gated behind environment, recipient allowlist, and mutation opt-in settings.4MIT

Winnr MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage cold-email infrastructure through natural language, covering domain and mailbox provisioning, DNS setup, email warming, inbox and reply triage, exports, pre-warmed domain purchases, and webhooks. Supports hosted OAuth or local stdio installs with scoped read, write, and purchase permissions, plus two-step confirmation for anything that charges a card.45 PyPIMIT
Allowance MCPofficial
FlicenseNot gradedqualityDmaintenanceEnables AI agents to request purchase approval from humans, receive scoped virtual cards, complete checkout, and report receipts for audit.-- AlicenseAqualityBmaintenanceEnables customers to consult their own orders from Claude or ChatGPT, including status, items, totals, and history, with per-customer permissions and admin tools for order creation, state updates, and summaries.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage contacts, build audiences, create and edit email drafts and automations, read reports, and schedule approved sends within an email marketing workspace.1MIT

Send4 MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceConnects AI assistants to a Send4 workspace so users can ask about flows, campaigns, conversations, and usage, and make permitted changes in natural language.1MIT
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.