Ext Ops Panel
Open dashboard
Comparison

spec-to-code vs Agentic SDLC MCP

spec-to-code is a plugin bundle for AI coding tools published by vkroz. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Agentic SDLC MCP is an MCP server published by SakuraCianna. 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

Where each is published
Marketplacespec-to-codeAgentic SDLC MCP
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.11.0
Downloads/month (npm): 314
Downloads/week (npm): 58
Forks (GitHub): 0
Stars (GitHub): 1
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

spec-to-code vs Agentic SDLC MCP
Factspec-to-codeAgentic SDLC MCP
Marketplaces that list it11
Stars (GitHub) (differs)2 (better)1 (worse)
Forks (GitHub)00
Last release (differs)Not published2026-10-14
Where it runs (differs)Installs as a plugin bundleOn your machine (agentic-sdlc-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 1
Parts of the bundle (differs)15Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/vkroz/spec-to-codegithub.com/sakuracianna/agentic-sdlc-mcp
Changes in the last 7 days00
First seen (differs)2026-10-122026-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

spec-to-code

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

Accelerates software delivery by automating SDLC stages inside Claude Code — Claude facilitates writing specs and designing architecture, then autonomously builds implementation plans, implements and tests the product — all driven by 13 structured /stc:* commands with built-in review gates and document consistency.

Agentic SDLC MCP

In its own words, on Official MCP Registry:

Agentic SDLC governance and security controls for AI coding agents working with GitHub.

How to run each

spec-to-code As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install spec-to-code@claude-community

Agentic SDLC MCP As a local MCP server: npm package

Claude Code
claude mcp add --env "GITHUB_TOKEN=<YOUR_GITHUB_TOKEN>" --transport stdio agentic-sdlc-mcp -- npx -y agentic-sdlc-mcp

Requires: GITHUB_TOKEN (secret)

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 spec-to-code publish no settings it asks for, so we do not compare settings.

What it can do: spec-to-code · What it can do: Agentic SDLC 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