Ext Ops Panel
Open dashboard
Comparison

wordpress-mcp vs Lindo AI

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). Lindo AI is an MCP server published by lindoai. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-16. 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
Marketplacewordpress-mcpLindo AI
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 2
Stars (GitHub): 9
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 1.1.1
Downloads/month (npm): 594
Downloads/week (npm): 73
Forks (GitHub): 0
Stars (GitHub): 3
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

wordpress-mcp vs Lindo AI
Factwordpress-mcpLindo AI
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)9 (better)3 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)47
Licence (differs)Not statedMIT
Repository (differs)github.com/msapps-mobile/claude-pluginsgithub.com/lindoai/mcp-server
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago

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

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

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.

Lindo AI

In its own words, on Official MCP Registry:

Create and manage Lindo AI websites, pages, blogs, clients, and credits from any MCP client.

How to run each

wordpress-mcp As a Claude Code plugin

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

Lindo AI As a remote MCP server

Claude Code
claude mcp add --transport http lindo-ai https://mcp.lindo.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: LINDO_API_KEY (secret), Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Lindo AI 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 wordpress-mcp publish no settings it asks for, so we do not compare settings.

What it can do: wordpress-mcp · What it can do: Lindo AI · 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