Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Query and manage Paddle Billing: pricing, subscriptions, payments, revenue reports and webhooks.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.paddle.com/mcpRun this in your terminal
claude mcp add --transport http paddle https://mcp.paddle.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"paddle": {
"url": "https://mcp.paddle.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"paddle": {
"type": "http",
"url": "https://mcp.paddle.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.paddle.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain paddle.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 64 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Python MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Local-only Python MCP server for the Files.com API.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Give any AI assistant direct access to the Paddle API over the Model Context Protocol.
This server gives AI assistants like Claude, Cursor, and Windsurf direct access to Paddle API operations: products, prices, subscriptions, customers, transactions, and more. Paddle hosts it, so there's nothing to install or run. This repository holds the setup instructions only, with no source code.
Three tools are exposed to your assistant: search the API reference, execute chained API calls in a sandbox, and report_missing_tool for telemetry. A fourth tool, show_metrics_chart, draws a metric as an interactive chart in clients that support MCP Apps.
A single MCP endpoint. Each host serves one environment:
| Environment | Endpoint | Authentication |
|---|---|---|
| Live | POST https://mcp.paddle.com/mcp | OAuth or API key |
| Sandbox | POST https://sandbox-mcp.paddle.com/mcp | API key |
The examples below add both, as paddle-live and paddle-sandbox, so you can tell your assistant which one to use.
There are two ways to authenticate: sign in with OAuth, or pass a Paddle API key as a bearer token.
OAuth (recommended). Point your client at the endpoint with no credentials. The first time it connects, a browser window opens and you sign in to Paddle, so there's no API key to create, copy, or keep in a config file.
API key. Prefer a long-lived credential, or running somewhere a browser can't open? Pass a Paddle API key in the Authorization header on every request:
Authorization: Bearer <your-paddle-api-key>
Scope the key to the permissions you actually need. They are the only limit on what the assistant can do.
Sandbox connects with a sandbox API key (prefixed pdl_sdbx_), passed in the Authorization header on every request. The sandbox server doesn't support OAuth.
Authorization: Bearer <your-sandbox-api-key>
Scope the key to the permissions you actually need. They are the only limit on what the assistant can do.
Drop one of these configurations into your AI client. paddle-live carries no credentials, so your client runs the OAuth flow on first connect. Replace SANDBOX_API_KEY with your sandbox key.
To connect to live with an API key instead, give paddle-live the same Authorization header as paddle-sandbox, with your live key.
claude mcp add --transport http paddle-live https://mcp.paddle.com/mcp
claude mcp add --transport http paddle-sandbox https://sandbox-mcp.paddle.com/mcp --header "Authorization: Bearer SANDBOX_API_KEY"
Then run /mcp inside Claude Code to start the browser sign-in.
In claude_desktop_config.json:
{
"mcpServers": { "paddle-live": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.paddle.com/mcp"] }, "paddle-sandbox": { "command": "npx", "args": [ "-y", "mcp-remote", "https://sandbox-mcp.paddle.com/mcp", "--header", "Authorization: Bearer SANDBOX_API_KEY" ] } } }
codex mcp add paddle-live --url https://mcp.paddle.com/mcp
codex mcp login paddle-live
export PADDLE_SANDBOX_API_KEY="SANDBOX_API_KEY" codex mcp add paddle-sandbox --url https://sandbox-mcp.paddle.com/mcp --bearer-token-env-var PADDLE_SANDBOX_API_KEY
In ~/.cursor/mcp.json:
{
"mcpServers": { "paddle-live": { "type": "http", "url": "https://mcp.paddle.com/mcp" }, "paddle-sandbox": { "type": "http", "url": "https://sandbox-mcp.paddle.com/mcp", "headers": { "Authorization": "Bearer SANDBOX_API_KEY" } } } }
Press Cmd/Ctrl + Shift + P , choose MCP: Open workspace folder MCP configuration, then edit mcp.json:
{
"servers": { "paddle-live": { "type": "http", "url": "https://mcp.paddle.com/mcp" }, "paddle-sandbox": { "type": "http", "url": "https://sandbox-mcp.paddle.com/mcp", "headers": { "Authorization": "Bearer SANDBOX_API_KEY" } } }, "inputs": [] }
ChatGPT connects via Plugins rather than a config file. Custom MCP apps need a paid plan (Plus, Pro, Business, Enterprise, or Edu) with Developer mode enabled. They aren't available on the free tier.
https://mcp.paddle.com/mcp or https://sandbox-mcp.paddle.com/mcp.Authorization: Bearer API_KEY.For more detailed setup instructions, see the full installation guide.
Ask your assistant in plain language, and name the server so it picks the right environment. For example:
Using paddle-sandbox, set up a Pro plan at $79/month with a 14-day trial, then show me the products and prices.
Using paddle-live, investigate the failed payment for sarah@example.com and tell me whether it's recurring.
Using paddle-live, chart my revenue for the last 3 months by week.
For more example prompts and best practices, see the Paddle MCP server docs.