Ext Ops Panel
Open dashboard
Comparison

SPM for Codex vs io.github.PaulRichez/devkit-for-strapi-mcp

SPM for Codex is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.

SPM for Codex is a plugin bundle for AI coding tools published by Manna Digital Consulting, S.L.. No marketplace we read lists it any more. io.github.PaulRichez/devkit-for-strapi-mcp is an MCP server published by PaulRichez. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-25. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceSPM for Codexio.github.PaulRichez/devkit-for-strapi-mcp
Community marketplace getspm/spm-agent-connectors Removed on 2026-10-15
Version: 0.1.0+codex.20260814165946
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.2
Downloads/month (npm): 573
Downloads/week (npm): 236
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.2.2
Downloads/month (npm): 573
Downloads/week (npm): 236
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

SPM for Codex vs io.github.PaulRichez/devkit-for-strapi-mcp
FactSPM for Codexno longer listed · io.github.PaulRichez/devkit-for-strapi-mcp
Marketplaces that list it (differs)02
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)Not published2026-10-15
Where it runs (differs)Remote server (getspm.com/v1/mcp)On your machine (devkit-for-strapi-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Hooks it runs (differs)3Not published
Parts of the bundle (differs)5Not a bundle
Licence (differs)Not statedMIT AND LicenseRef-PolyForm-Shield-1.0.0
Repository (differs)github.com/getspm/spm-agent-connectorsgithub.com/paulrichez/devkit-for-strapi
Changes in the last 7 days00
First seen (differs)2026-10-132026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of SPM for Codex

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • Codex Copilot

    Codex-native software specialist framework with tc-backed workflow discipline and Claude Copilot parity contracts.

    by Everyone Needs A Copilot · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • PAPI: Persistent Adaptive Project Intelligence

    Adaptive plan/build/review cycles for AI coding assistants, persisted across sessions.

    by getpapi · MCP server

    Listed on: Official MCP Registry, Community GitHub marketplaces · Describes nearly the same job

  • devpace

    Never re-explain your project to Claude again. devpace remembers context across sessions, manages requirement changes, and ensures quality gates — all automatically. Zero setup…

    by paceforge · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • Qodo

    Bring Qodo's codebase intelligence, coding standards, and code review into your coding agent.

    by qodo-ai · Plugin bundle

    Listed on: Claude Code: claude-plugins-official, Claude: knowledge-work-plugins, Community GitHub marketplaces · Describes nearly the same job

  • project-scaffolder-synaptic-edition

    Generate a complete project knowledge base from a single brief, then orchestrate development with an AI project leader, quality pipeline, and skills that learn from experience…

    by valsecchi75 · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • Codemium

    Execution Intelligence, Anti-Slop Intelligence, Polyglot structural intelligence, bounded context, scoped changes, persistent Project Brain, and risk-aware verification for Claude…

    by Codemium · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

SPM for Codex

In its own words, on Community GitHub marketplaces:

Connect Codex to Structured Project Memory through the hosted SPM MCP endpoint.

io.github.PaulRichez/devkit-for-strapi-mcp

In its own words, on Official MCP Registry:

Strapi codebase intelligence for AI agents (not content CRUD): real UIDs, schemas, refs, refactors.

How to run each

SPM for Codex

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

io.github.PaulRichez/devkit-for-strapi-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "DEVKIT_LICENSE_KEY=<YOUR_DEVKIT_LICENSE_KEY>" --transport stdio devkit-for-strapi-mcp -- npx -y devkit-for-strapi-mcp

Requires: DEVKIT_LICENSE_KEY (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 SPM for Codex publish no settings it asks for, so we do not compare settings.

What it can do: SPM for Codex · What it can do: io.github.PaulRichez/devkit-for-strapi-mcp · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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