tray-api vs Swell MCP
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). Swell MCP is an MCP server published by devkindhq. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  tray-api |  Swell MCP |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 2.1.0 Forks (GitHub): 0 Stars (GitHub): 15 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.0 Downloads/month (npm): 169 Downloads/week (npm): 10 Forks (GitHub): 1 Stars (GitHub): 2 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 | tray-api | Swell MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 15 (better) | 2 (worse) |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@tray-tecnologia/tray-api-plugin) | On your machine (swell-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 2, secrets among them: 1 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 47 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/tray-tecnologia/tray-api-claude-plugin | github.com/devkindhq/swell-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
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
tray-api
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.
Swell MCP
Model Context Protocol server for Swell e-commerce platform integration with AI assistants
How to run each
tray-api As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install tray-api@claude-communitySwell MCP As a local MCP server: npm package
claude mcp add --env "SWELL_SECRET_KEY=<YOUR_SWELL_SECRET_KEY>" --env "SWELL_STORE_ID=<YOUR_SWELL_STORE_ID>" --transport stdio swell -- npx -y swell-mcpRequires: SWELL_SECRET_KEY (secret), SWELL_STORE_ID
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only tray-api asks for
OPT_OUT_INSTRUMENTATION
Only Swell MCP asks for
SWELL_SECRET_KEY (secret)SWELL_STORE_ID
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: tray-api · What it can do: Swell MCP · 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.