wordpress-mcp vs NomaCMS MCP Server
wordpress-mcp is a plugin bundle for AI coding tools published by MSApps-Mobile. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). NomaCMS MCP Server is an MCP server published by NomaCMS. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
| Marketplace |  wordpress-mcp |  NomaCMS MCP Server |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.1.0 Forks (GitHub): 2 Stars (GitHub): 10 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.2.2 Downloads/month (npm): 156 Downloads/week (npm): 28 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
| Fact | wordpress-mcp | NomaCMS MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 10 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 2 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@nomacms/mcp-server) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/msapps-mobile/claude-plugins | github.com/nomacms/nomacms-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-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
wordpress-mcp
Manage WordPress sites directly from Claude using the WordPress MCP Adapter. Connect Claude to any WordPress 6.9+ site and manage content, users, settings, and WooCommerce — all through conversation.
NomaCMS MCP Server
MCP server for NomaCMS. Manage collections, fields, content, assets, and webhooks via AI agents.
How to run each
wordpress-mcp As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install wordpress-mcp@claude-communityNomaCMS MCP Server As a local MCP server: npm package
claude mcp add --env "NOMA_API_KEY=<YOUR_NOMA_API_KEY>" --env "NOMA_PROJECT_ID=<YOUR_NOMA_PROJECT_ID>" --transport stdio nomacms-mcp-server -- npx -y @nomacms/mcp-serverRequires: NOMA_API_KEY (secret), NOMA_PROJECT_ID
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 wordpress-mcp publish no settings it asks for, so we do not compare settings.
What it can do: wordpress-mcp · What it can do: NomaCMS MCP Server · 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.