Ext Ops Panel
Open dashboard
Comparison

Stripe vs tray-api

Stripe is an MCP server published by stripe. Marketplaces we read that list it: 1 (Docker MCP Catalog). tray-api is a plugin bundle for AI coding tools published by tray-tecnologia. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-17. 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

Where each is published
MarketplaceStripetray-api
Docker MCP Catalog Listed
Version: sha256:92ba43f82377
Forks (GitHub): 370
Pulls (Docker Hub): 45 730
Stars (Docker Hub): 9
Stars (GitHub): 1 952
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 2.1.0
Forks (GitHub): 0
Stars (GitHub): 15
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

Stripe vs tray-api
FactStripetray-api
Marketplaces that list it11
Stars (GitHub) (differs)1 952 (better)15 (worse)
Pulls (Docker Hub) (differs)45 730No figure on Docker Hub
Forks (GitHub) (differs)370 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/stripe)On your machine (@tray-tecnologia/tray-api-plugin)
Transport (differs)stdioNot stated
Tools it declares (differs)22Not published
Environment variables it asks for (differs)1, secrets among them: 11, secrets among them: 0
Hooks it runs (differs)Not published1
Parts of the bundle (differs)Not a bundle47
LicenceMITMIT
Repository (differs)github.com/stripe/agent-toolkitgithub.com/tray-tecnologia/tray-api-claude-plugin
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-12

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

Stripe

In its own words, on Docker MCP Catalog:

Interact with Stripe services over the Stripe API.

tray-api

In its own words, on Claude Code: claude-plugins-community:

Complete plugin for integrating with the Tray E-commerce platform APIs. Provides 34 skills, 5 specialized agents, and 3 commands covering 150+ endpoints. Includes OAuth authentication flows, catalog and order management, shipping and payment configuration, webhooks, migration from other platforms (Shopify, WooCommerce, Magento, VTEX, Nuvemshop), and integration validation for app certification.

How to run each

Stripe As a local MCP server: Docker image

Claude Code
claude mcp add --env "STRIPE_SECRET_KEY=<YOUR_STRIPE_SECRET_KEY>" --transport stdio stripe -- docker run -i --rm -e STRIPE_SECRET_KEY mcp/stripe

Requires: STRIPE_SECRET_KEY (secret)

tray-api As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install tray-api@claude-community

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of tray-api publish no list of tools, so we do not compare tools.

Settings each asks for

Only Stripe asks for

  • STRIPE_SECRET_KEY (secret)

Only tray-api asks for

  • OPT_OUT_INSTRUMENTATION

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Stripe · What it can do: tray-api · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built