Ext Ops Panel
Open dashboard
Comparison

devrunway vs xpay DevTools

devrunway is a plugin bundle for AI coding tools published by manikumarkv. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). xpay DevTools is an MCP server published by xpaysh. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
Marketplacedevrunwayxpay DevTools
Claude Code: claude-plugins-community Listed
Version: 4.0.5
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

devrunway vs xpay DevTools
Factdevrunwayxpay DevTools
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (devtools.mcp.xpay.sh/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)12, secrets among them: 7Not published
Hooks it runs (differs)35Not published
Parts of the bundle (differs)55Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/manikumarkv/devrunway-claude-plugingithub.com/xpaysh/mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

devrunway

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

Modular SDLC plugin for any tech stack. Run /setup to declare your tools (frontend, backend, DB, auth, CI, etc.), and devrunway installs only the matching standards, pre-wires MCP servers, and activates a runtime of 35 hooks that block secrets, enforce conventional commits, and catch SQL injection, XSS, PII-in-logs, and more on every save.

xpay DevTools

In its own words, on Official MCP Registry:

30+ dev tools. Context7, Code Runner, Python Execute, Code Sentinel, NPM Sentinel, PlantUML.

How to run each

devrunway As a Claude Code plugin

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

xpay DevTools

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

The marketplaces of xpay DevTools publish no settings it asks for, so we do not compare settings.

What it can do: devrunway · What it can do: xpay DevTools · 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