MCP Server for Paddle Billing

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Paddle MCP Server?

Paddle MCP Server is a server designed for interacting with the Paddle Billing API, which handles payments, taxes, subscriptions, and metrics through a unified API.

How to use Paddle MCP Server?

To use the Paddle MCP Server, you need to create an API key in the Paddle Developer tools and run the server using the command: npx -y @paddle/paddle-mcp --api-key=PADDLE_API_KEY --environment=(sandbox|production).

Key features of Paddle MCP Server?

  • List products in your Paddle catalog
  • Create new products and prices
  • List customers, transactions, and subscriptions
  • Generate custom financial reports

Use cases of Paddle MCP Server?

  1. Managing product listings and pricing in Paddle.
  2. Analyzing financial data through custom reports.
  3. Integrating Paddle Billing with other applications using the MCP protocol.

FAQ from Paddle MCP Server?

  • What is the difference between Paddle MCP and Paddle Classic?

Paddle MCP is designed for the new Paddle Billing API, while Paddle Classic refers to the older API.

  • Is there a sandbox environment for testing?

Yes, you can use the sandbox environment for testing your integration before going live.

  • What programming language is used for Paddle MCP Server?

Paddle MCP Server is built using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 hours ago