Ext Ops Panel
Open dashboard
Comparison

tray-api vs Spree Commerce developer docs for AI agents

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). Spree Commerce developer docs for AI agents is an MCP server published by spree. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. 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
Marketplacetray-apiSpree Commerce developer docs for AI agents
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.0.0
Forks (GitHub): 5 320
Stars (GitHub): 15 831
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

tray-api vs Spree Commerce developer docs for AI agents
Facttray-apiSpree Commerce developer docs for AI agents
Marketplaces that list it11
Stars (GitHub) (differs)15 (worse)15 831 (better)
Forks (GitHub) (differs)0 (worse)5 320 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@tray-tecnologia/tray-api-plugin)Remote server (spreecommerce.org/docs/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)47Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/tray-tecnologia/tray-api-claude-plugingithub.com/spree/spree
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-30
Endpoint at the last check (differs)no remote endpoint we checkResponded 6 h ago

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

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.

Spree Commerce developer docs for AI agents

In its own words, on Official MCP Registry:

Spree Commerce docs for AI coding agents: build headless B2B and marketplace ecommerce on its APIs.

How to run each

tray-api As a Claude Code plugin

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

Spree Commerce developer docs for AI agents As a remote MCP server

Claude Code
claude mcp add --transport http ecommerce-docs https://spreecommerce.org/docs/mcp

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

Only Spree Commerce developer docs for AI agents 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

The marketplaces of Spree Commerce developer docs for AI agents publish no settings it asks for, so we do not compare settings.

What it can do: tray-api · What it can do: Spree Commerce developer docs for AI agents · 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.

Where the data comes from: how the catalog is built