The era of writing API calls to manage your store is over. Meet Fungies MCP — the official Model Context Protocol server that lets AI assistants like Claude, Cursor, and ChatGPT operate your Fungies store through natural language.
Payments are one of the most friction-heavy parts of running a digital business. Refunding an order means navigating a dashboard. Spinning up a new pricing tier for a promotion requires knowing the right API endpoint. Verifying a webhook signature means digging into docs. These are solvable problems — but they burn time that should go toward building your product.
That changes today. We are launching Fungies MCP: the official Model Context Protocol server for the Fungies Merchant of Record platform. Once you connect it to your AI coding assistant, your entire Fungies payment infrastructure becomes accessible through conversation.
Ask “How much did I make last week?” and get an answer. Say “Create a $29/year plan for my course” and watch it happen. Type “What is the status of order 9XMrb9Hk?” — done. No API docs. No dashboard hunting. Just plain English.
What Is MCP and Why Does It Matter for Payments?
Model Context Protocol (MCP) is an open standard developed by Anthropic that allows AI assistants to call external tools and services in a structured, secure way. Think of it as a universal plugin system for AI agents — instead of your AI being limited to answering questions about static knowledge, it can take real actions in real systems.
For payments, this is a significant shift. Traditional payment integrations require developers to read documentation, authenticate against APIs, construct request payloads, handle errors, and parse responses — all manually, in code. MCP flips that model entirely. You describe what you want in natural language, and the AI handles the API complexity underneath.
Fungies MCP exposes 40 tools covering every major area of the Fungies platform — from product catalog management to subscription lifecycle control to payment history. Whether you are a solo creator managing a digital downloads store or a SaaS team handling thousands of subscriptions, the MCP gives your AI assistant the same capabilities you would get from a dedicated Fungies engineer sitting next to you.
Full Capabilities: What the Fungies MCP Can Do
The Fungies MCP is organized across 10 core capability areas, covering the complete lifecycle of a digital commerce operation:
| Capability Area | What Your AI Can Do | Example Prompt |
|---|---|---|
| Catalog Management | List, search, create, update, duplicate, and archive products | “Show me all my active products with their prices” |
| Pricing & Offers | Create and update price points, configure recurring plans, manage inventory | “Create a $49/month Pro plan and a $399/year annual option” |
| Orders | Look up orders by ID or short number, filter by status/date, cancel pending orders | “What is the status of order 9XMrb9Hk?” |
| Payments | View all transactions filtered by PAID / FAILED / REFUNDED, inspect individual payment details including fees and tax | “Show me all failed payments in the last 7 days” |
| Subscriptions | Pause, resume, cancel, upgrade/downgrade, or charge usage-based extras on active subscriptions | “Pause the subscription for customer ID 9923 for 30 days” |
| Customers | Find accounts by email, view purchase history and full inventory, create or update customer records | “What has user [email protected] purchased in the last 6 months?” |
| Promotions | Create coupon codes and automatic sale discounts, update validity windows, archive expired promotions | “Create a 30% off coupon LAUNCH30 valid for 7 days” |
| Game Keys & Licenses | Upload license key inventory to an offer, remove unsold keys, track sold vs. available stock | “How many Steam keys do I have left for the Indie Bundle offer?” |
| Checkout Elements | List embeddable checkout widgets, create new checkout elements binding sets of offers | “Create a checkout element for my Pro and Enterprise offers” |
| Webhook Signature Verification | Verify a Fungies webhook signature locally using HMAC-SHA256 — no network call required | “Here’s a webhook body and x-fngs-signature header — is the signature valid?” |
In read-only mode (using only your public key), the MCP exposes 18 tools covering analytics, reporting, and exploration with zero ability to create, modify, or delete anything. In full access mode (public + secret key), all 40 tools are available — including create, update, cancel, and archive operations.
A note on webhook delivery logs: The webhooks_verify tool performs local cryptographic signature verification (HMAC-SHA256, timing-safe) — it does not require a network call and does not expose delivery history. If you need to browse past webhook deliveries, that is available in the Fungies dashboard under Developers → Webhooks.
How to Set Up Fungies MCP in Under 2 Minutes
Setup is intentionally minimal. There is no local installation, no Node.js server to run, no Docker container. Everything routes through the hosted endpoint at https://mcp.fungies.io/mcp.
Step 1: Get Your API Keys
- Log in at app.fungies.io
- Navigate to Developers → API Keys
- Click Create key pair — name it something like
Cursor MCPorClaude AI - You will receive two values: a
pub_...public key (safe to use in config files) and asec_...secret key (keep private; unlocks write operations)
Best practice: Create a dedicated key pair just for the MCP. If you ever want to revoke access, you can do it from the dashboard without touching any other integration.
Step 2: Connect to Your AI Tool
Cursor (One-Click — Recommended)
Visit mcp.fungies.io/install, paste your keys, and click Install. Cursor opens automatically and asks you to confirm. Your keys never leave your browser — the install page assembles the config locally and hands it off via a deep link.
Claude Desktop: Go to Settings → Connectors → Add custom connector. Set the URL to https://mcp.fungies.io/mcp and add your keys under Advanced → Custom headers.
Claude Code (CLI):
claude mcp add --transport http fungies https://mcp.fungies.io/mcp \
--header "x-fngs-public-key: pub_YOUR_PUBLIC_KEY" \
--header "x-fngs-secret-key: sec_YOUR_SECRET_KEY"VS Code (GitHub Copilot Chat), Windsurf, Continue.dev, OpenAI Codex CLI, and Zed are all supported. Full configs are in the GitHub README.
Step 3: Test It
Ask your AI assistant: “List my five most recent products on Fungies.” If you see your products listed, you are live.
Fungies MCP vs Other Payment MCPs: A Clear Comparison
The MCP ecosystem for payments is growing. Stripe has their own MCP server. Paddle has tooling in development. But there are meaningful differences — especially if you are selling digital goods, running subscriptions, or operating globally.
| Feature | Fungies MCP | Stripe MCP | Paddle MCP |
|---|---|---|---|
| Merchant of Record | ✅ Full MoR — tax, VAT, compliance handled | ❌ Not MoR — you handle taxes | ✅ MoR for select markets |
| VAT/GST automation | ✅ Automatic globally | ❌ Manual tax configuration required | ✅ Limited markets |
| Digital goods native | ✅ Built for digital files, keys, subscriptions | ⚠️ General purpose | ⚠️ General purpose |
| Game key fulfillment | ✅ Upload, track, ship license keys via AI | ❌ Not supported | ❌ Not supported |
| Total MCP tools | ✅ 40 tools | ~30 tools | Limited (early stage) |
| Read-only mode | ✅ 18 safe read-only tools | ✅ Available | ⚠️ Partial |
| Self-host option | ✅ Full self-hosting supported | ❌ | ❌ |
| One-click install | ✅ mcp.fungies.io/install | ❌ Manual only | ❌ Manual only |
| Webhook signature verify | ✅ Local HMAC-SHA256, no network call | ⚠️ Limited | ❌ |
| Pricing | From 0% platform fee on custom plans | 0.5–0.7% + Stripe fees | 5% + payment fees |
The core difference comes down to who is responsible for the hard parts. With Stripe, you are a Payment Facilitator — you use their infrastructure but you own the tax compliance, fraud liability, and regulatory complexity. With Fungies as your Merchant of Record, Fungies absorbs all of that. Your AI assistant using the Fungies MCP can cancel orders, create plans, and manage customers — without you needing to worry about whether that action affects your VAT liability in Germany.
Why This Is a Big Deal for AI Agents
Here is something worth pausing on: Fungies MCP is not just useful for humans asking questions in a chat interface. It is equally — arguably more — important for autonomous AI agents.
We are entering a period where software agents do not just answer questions; they run workflows. An agent might monitor your churn metrics, identify at-risk subscribers, and proactively apply retention discounts. Another might watch your license key inventory, detect when stock drops below a threshold, and alert you before fulfillment fails. A third might reconcile your weekly revenue, flag discrepancies, and generate a CFO-ready report — without you touching a spreadsheet.
All of this requires the agent to have reliable, structured access to your payment infrastructure. That is exactly what Fungies MCP provides.
Because the MCP is built on an open standard, any AI system that supports the Model Context Protocol can become a capable Fungies operator. This includes:
- Autonomous coding agents (Cursor, Claude Code, Windsurf) that can manage your store between coding sessions
- Business intelligence agents that pull revenue data on a schedule and surface insights proactively
- Customer support agents that can look up order history, check payment status, and validate subscription state in real time — without human escalation
- Marketing automation agents that can spin up coupon codes for campaigns, track redemption rates, and deactivate expired promotions automatically
The pattern is the same in each case: the agent expresses intent in structured natural language, Fungies MCP translates that into the right API calls, and the platform executes. No custom code. No integration maintenance. No API versioning headaches. This is what it looks like when payment infrastructure becomes truly composable.
Security and Safety
Giving an AI assistant access to your payment platform naturally raises questions about risk. The Fungies MCP is designed with several safety layers:
Two-mode access model. Read-only mode (public key only) gives access to 18 tools — analytics, lookups, and reporting with zero ability to create, modify, or delete anything. Full access mode unlocks all 40 tools. You choose the level of trust.
Destructive confirm gate. Archive, cancel, and remove-key tools require the caller to explicitly pass confirm: true — your AI cannot accidentally wipe data without you approving the action first.
Dedicated key pairs. Create a separate API key pair for MCP use. If you ever suspect misuse, revoke that specific key from the dashboard — your main API integration is unaffected.
Keys stay local. The one-click install page assembles your config entirely in the browser. Your keys are never transmitted to Fungies servers during setup — and they never appear in server logs (strict redaction is enforced).
Self-hosting available. For teams with stricter security requirements, the full MCP server source is available to self-host on your own infrastructure as a single Docker container.
Example Prompts to Get You Started
Revenue & Analytics: “How many paid orders did I have in the last 7 days, broken down by product?” / “Show me my 10 biggest customers by lifetime spend.” / “Which subscription offers have the highest churn this quarter?”
Catalog & Pricing: “Duplicate my Pro Plan and call the copy Pro Plan — EUR, then create a €99/year offer for it.” / “List every offer priced under $5.” / “Create a $19/month Starter plan and a $49/month Pro plan.”
Orders & Customers: “What is the payment status of order 9XMrb9Hk?” / “Find the customer with email [email protected], show me her inventory, and cancel any active subscriptions at period end.” / “Show me all failed payments in the last 24 hours.”
Promotions & Subscriptions: “Create a 25% off coupon code WINTER25 valid through January 15th.” / “Archive all coupons whose validity window ended before this year.” / “Pause the subscription for customer ID 8821 for 2 months.”
Webhook Verification: “Here is a webhook body and the x-fngs-signature header — tell me if the signature is valid given my signing secret.” (Signature check runs locally — no network call, no logs.)
The Bigger Picture: Payment Infrastructure as a Language
The launch of Fungies MCP is part of a broader shift in how developers and operators interact with infrastructure. The best APIs in the world are still APIs — they require code, context, and maintenance. Natural language interfaces change the access model entirely.
When a non-technical team member can ask “How many license keys do we have left?” and get an accurate answer from a live system — not a Google Sheet that may be out of date — the value of the underlying platform multiplies.
When a developer building a new product can say “Set up a $9/month subscription plan with a 30-day trial and generate me a coupon code for the launch” and watch it happen in seconds — the friction of payment infrastructure drops to near zero.
And when an autonomous agent can monitor subscription health, flag at-risk accounts, and apply targeted retention offers without a human in the loop — the leverage from good payment infrastructure becomes exponential.
Fungies MCP is available today. It is free to use for all Fungies accounts. Getting started takes less than two minutes.
→ Install Fungies MCP
→ View the GitHub repository
→ Read the full documentation
Questions? Join the Fungies Discord or open an issue on GitHub. We read everything.
