paddle
No liveness check has reached it yet; it has been in the index since 10 Oct 2026. How this is checked
Paddle MCP Server exposes four MCP tools for retrieving Paddle customers, subscriptions, transactions, and adjustments. It provides a JSON-RPC HTTP endpoint for developers and AI agents that need structured access to Paddle billing data.
Inferred · not functionally tested
Overview
6 featuresPurpose: Querying Paddle billing and revenue records through an MCP-compatible interface.
Inferred · not functionally tested
Audience: developers building AI agents and integrations with Paddle billing data
Inferred · not functionally tested
Functions: data_extraction
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: unknown · Self-hosting: unknown
Recorded constraints: pricing: unknown · license: Proprietary · platforms: WEB · deployment: browser, api_only, cloud_managed
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: gateway.pipeworx.io. These links do not verify the individual claims.
paddle is an API design, testing & docs project. Inferred · not functionally tested: It focuses on querying Paddle billing and revenue records through an MCP-compatible interface. Inferred · not functionally tested: It is built as a B2B product for developers building AI agents and integrations with Paddle billing data. Basis unknown · not verified: paddle is available on the web and API.
It is developed by Pipeworx. Inferred · not functionally tested: Key capabilities include customer lookup, subscription listing, and transaction listing. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Customer lookup
- Subscription listing
- Transaction listing
- Adjustment listing
- JSON-RPC endpoint
- MCP tools
Topics: Inferred · not functionally tested
Built with & integrations
- Cloudflare
- cf-ray header
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed10 Oct · 00:02 UTCPaddle seen via MCP Registry (official)Source: MCP Registry (official) · Open
Frequently asked questions about paddle
- What does paddle do?
- Inferred · not functionally tested: Paddle focuses on querying Paddle billing and revenue records through an MCP-compatible interface. It is catalogued under API design, testing & docs on PulseGate.
- Who should use paddle?
- Inferred · not functionally tested: paddle is a B2B product built for developers building AI agents and integrations with Paddle billing data.
- What platforms does paddle run on?
- Basis unknown · not verified: paddle runs on the web and API.
- Is paddle still active?
- Unverified. paddle has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
- What are alternatives to paddle?
- Similar projects tracked by PulseGate include pipedrive, pacer, and discord.pipedrivepacerdiscord
- Who develops paddle?
- paddle is developed by Pipeworx.
- Does paddle have an API or integrations?
- Inferred · not functionally tested: Yes — paddle exposes an MCP server and a public API.
Similar projects
Closest matches by what these projects do