paddle vs SparkPay
paddle is a plugin bundle for AI coding tools published by PaddleHQ. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). SparkPay is an MCP server published by sparkpay.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-06. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  paddle |  SparkPay |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: de7fcd3 Forks (GitHub): 2 Stars (GitHub): 9 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | paddle | SparkPay |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 | No figure on GitHub |
| Forks (GitHub) (differs) | 2 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (sparkpay.dev/api/mcp/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 13 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/paddlehq/paddle-agent-skills | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 4 days ago returned HTTP 401 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
paddle
The Paddle plugin connects Claude Code to Paddle Billing, a merchant of record for SaaS, AI, mobile app, and digital product businesses. It provides step-by-step guidance for the most common Paddle integration tasks and wires up the Paddle docs MCP server so Claude pulls from up-to-date documentation as it works — helping you follow Paddle's recommended patterns for checkout, subscriptions, and webhooks instead of guessing from stale examples.
SparkPay
Stripe billing for indie apps: plans, coupons, subscriptions, customers and revenue reporting.
How to run each
paddle As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install paddle@claude-communitySparkPay As a remote MCP server
claude mcp add --transport http sparkpay https://sparkpay.dev/api/mcp/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only SparkPay has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: paddle · What it can do: SparkPay · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.