Ext Ops Panel
Open dashboard
Comparison

xsolla-ai-kit vs Swell MCP

xsolla-ai-kit is a plugin bundle for AI coding tools published by xsolla. 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-18. 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
Marketplacexsolla-ai-kitSwell MCP
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 6
Stars (GitHub): 7
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.0
Downloads/month (npm): 213
Downloads/week (npm): 38
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

xsolla-ai-kit vs Swell MCP
Factxsolla-ai-kitSwell MCP
Marketplaces that list it11
Stars (GitHub) (differs)7 (better)2 (worse)
Forks (GitHub) (differs)6 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (xsolla.mcp.kapa.ai)On your machine (swell-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)9Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/xsolla/xsolla-ai-kitgithub.com/devkindhq/swell-mcp
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)Responded 3 days agono remote endpoint we check

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

xsolla-ai-kit

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

Xsolla agent skills toolkit — guided, end-to-end workflows for merchant setup, catalog design, Login/NewID, Pay Station, webhooks, storefront build, and shop branding, calling Xsolla REST APIs directly.

Swell MCP

In its own words, on Official MCP Registry:

Model Context Protocol server for Swell e-commerce platform integration with AI assistants

How to run each

xsolla-ai-kit As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install xsolla-ai-kit@claude-community

Swell MCP As a local MCP server: npm package

Claude Code
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-mcp

Requires: 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.

Only xsolla-ai-kit 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 xsolla-ai-kit publish no settings it asks for, so we do not compare settings.

What it can do: xsolla-ai-kit · 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.

Where the data comes from: how the catalog is built