Skip to content

MCP servers › com.wpmcp-pro › wpmcp

MCP server · registry snapshot 2026-11-19 · last checked 2026-11-19

wpmcp MCP server

Registry name com.wpmcp-pro/wpmcp

by wpmcp-pro.com · domain (the registry's namespace rule)repository owner on GitHub: wpmcp (organization)Source ↗Website ↗

MCP server for WordPress, shipped as a plugin, with a snapshot and undo for every supported write — the publisher's description

5 of 5 record checks metversion 1.1.0PHPstreamable HTTP

Summary

com.wpmcp-pro/wpmcp is a remote MCP server listed in the official MCP registry at version 1.1.0, under the namespace of the domain wpmcp-pro.com. Its linked repository is github.com/wpmcp/wpmcp; GitHub reports its owner as wpmcp, an organization.

Record checks

5 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 4 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Repository
public
Last tested
not tested

Tool list

Not read: It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it. So there is no tool-list size and no result from the three APIs.

Add to your client

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
1.1.0, published 2026-11-19 (registry, as of the 2026-11-19 snapshot)
First listed version
2026-11-11 (earliest version still in the registry; older removed versions would be earlier)
Version history
5 versions listed, 2026-11-11 to 2026-11-19; 5 in the 90 days before the 2026-11-19 snapshot.
Most recent 5 versions
  • 1.1.0 · 2026-11-19
  • 1.0.1 · 2026-11-18
  • 1.0.0 · 2026-11-18
  • 0.9.1 · 2026-11-16
  • 0.9.0 · 2026-11-11
(versions still listed in the registry only)
Registry data
snapshot 2026-11-19
Package and repository
checked 2026-11-19

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 1.0.0 (published 2026-11-18) → 1.1.0 (published 2026-11-19), between the registry lists of 2026-11-18 and 2026-11-19.

The publisher’s GitHub release note for v1.1.0 (“WP MCP 1.1.0”), published 2026-11-19.

Read the release note (the publisher’s text, shown as plain text, cut at 4,000 characters)
## WP MCP 1.1.0

New integrations and core operations, and the fixes found in the 1.0 test pass. No new top-level tools: everything is an operation on an existing tool, and every write is snapshotted and undoable unless it says otherwise.

### New

- WPGraphQL (read): wpgraphql-query runs a GraphQL query as the signed-in user, with mutations and subscriptions refused and emails, phones and IPs masked; wpgraphql-get-schema summarises the schema (#704).
- Relevanssi and FiboSearch: settings, index status and top searches, and settings writes, off until the site turns them on (#700).
- Image optimization plugins (Smush, ShortPixel, EWWW Image Optimizer, Imagify): get-image-optimizer-status, and optimize-attachment for one image through the plugin itself, snapshotted first and off until the site turns it on (#693).
- Advanced Ads: list and read ads and placements; create (as a draft), update, enable and disable ads and point placements, off until the site turns it on (#688).
- Security plugin status (read): Sucuri Security, All In One WP Security and Limit Login Attempts Reloaded, counts and switches only, never IPs or user names (#695).
- BuddyBoss Platform: groups, members, activity and profile fields through the BuddyPress operations, and the forums linked to a group (#670).
- WP Simple Pay forms and Paid Member Subscriptions plans and members (read, members masked) (#666).
- With Pro: WooCommerce payment gateway health for Stripe, WooPayments and PayPal Payments (connected, test mode, webhook status and last error, never keys) (#661); Kadence Blocks and Spectra plugin settings and page CSS, settings writes off until the site turns them on (#648); Weglot and GTranslate languages and exclusions, GTranslate language changes off until the site turns them on (#690); WP Offload Media status per attachment (#701); Blocksy Companion extensions listed and switched on or off (#650); core privacy requests: list and read export and erasure requests, file new ones and mark them complete, writes off until the site turns them on (#714).
- Comments: moderate-comment moderates up to 100 comments in one call, each with its own undo point, and status recheck asks Akismet to check pending comments again (#718).
- list-sessions lists one user's login sessions with IPs anonymized (#715).
- Media: get-media and list-media report missing image sizes, and resize-media fills exactly the missing ones, also for up to 20 images in one call (#716).
- write-file writes binary files such as fonts and images with encoding base64, up to 5 MB; PHP, scripts and server configuration files are refused (#851).
- tools/list carries readOnlyHint, destructiveHint and idempotentHint annotations, and tools behind an opt-in name it (#630). Over stdio (wp mcp-stdio serve) the client is told when the tool list changes (#632).
- New governance setting to switch on the tools an update adds, applied on updates only and never to a tool switched off by hand (#853).

### Fixes

- A refusal for an operation that is off by default points to WP MCP > Opt-in operations when that screen lists it (#966).
- Refusals name the plugin an operation needs, even when none of that integration's plugins is active, and before asking for its opt-in (#980, #1041); an unknown operation name answers unknown_operation (#1036).
- Undoing a Formidable notification or confirmation edit works again and no longer leaves a duplicate action behind (#984).
- Amelia 2.4.15: a booking with notify:false no longer emails the customer (#962).
- The WP MCP admin menu sits just below Settings (#1026).
- Read-only and similar refusal messages read correctly for every value (#1029).
- Rank Math redirections that were never hit report last_access as null (#1051).
- The Kadence Blocks and Spectra settings opt-in is listed on the Opt-in operations screen (#1016).

### Known issue

 on WP MCP > Opt-in operations the privacy requests group shows without a readable name. It works as expected and is fixed in the next relea

The release on GitHub

Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19; release notes from the GitHub Releases API, checked 2026-11-19.

What it is

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

This entry needs values of your own (marked < > or { } in the config below), so there is no one-click link: paste the config and fill them in.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://{site_domain}/wp-json/mcp/wpmcp-server
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "wpmcp": {
      "url": "https://{site_domain}/wp-json/mcp/wpmcp-server"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "wpmcp": {
      "type": "http",
      "url": "https://{site_domain}/wp-json/mcp/wpmcp-server"
    }
  }
}
Claude Code
claude mcp add --transport http wpmcp "https://{site_domain}/wp-json/mcp/wpmcp-server"
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "wpmcp": {
      "type": "streamableHttp",
      "url": "https://{site_domain}/wp-json/mcp/wpmcp-server",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "wpmcp": {
      "httpUrl": "https://{site_domain}/wp-json/mcp/wpmcp-server"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.wpmcp]
url = "https://{site_domain}/wp-json/mcp/wpmcp-server"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "wpmcp": {
      "url": "https://{site_domain}/wp-json/mcp/wpmcp-server"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url "https://{site_domain}/wp-json/mcp/wpmcp-server" --transport http
  • The URL contains parts in { } that the entry marks as variables; replace them with your own values.
  • Optional settings the entry also lists (left out above): Authorization.
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-19. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Repository github.com/wpmcp/wpmcpOpens publiclymatchesapi.github.com · 2026-11-19

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
com.wpmcp-pro
GitHub owner
an organization (wpmcp)
Repository
github.com/wpmcp/wpmcp
Stars
4
Repository age
91–180 days
Last push
0–30 days ago
Archived
no
Security policy
owner's .github/SECURITY.md

Source: the registry entry and api.github.com · 2026-11-19; security policy read from GitHub · 2026-11-12.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

5 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 4 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-19 (security policy 2026-11-12). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about com.wpmcp-pro/wpmcp

Answered from the data above

Who publishes com.wpmcp-pro/wpmcp?

The registry ties the namespace com.wpmcp-pro to the domain wpmcp-pro.com; only its owner can publish under it. Its linked repository is github.com/wpmcp/wpmcp; GitHub reports its owner as wpmcp, an organization. These are facts from the registry and GitHub, not a rating.

Is com.wpmcp-pro/wpmcp safe to install?

We do not rate servers as safe or unsafe. 5 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has com.wpmcp-pro/wpmcp been security tested?

No. It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it.

Does com.wpmcp-pro/wpmcp publish a security policy?

Yes: its repository has a public security policy (github.com/wpmcp/.github/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Where is the source code of com.wpmcp-pro/wpmcp?

In github.com/wpmcp/wpmcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it. — the server's own choice

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-19; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
api.github.com · 2026-11-19
Hosting type
registry · 2026-11-19
MCP capability
not checked
not read (no session)
Transport
streamable HTTP
registry · 2026-11-19
Required credentials
none declared
registry · 2026-11-19 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-19
Lifecycle status
registry · 2026-11-19
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: an organization · repository age: 91–180 days · stars: 0–9
api.github.com · 2026-11-19
Maintenance
api.github.com · 2026-11-19
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-19

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.wpmcp-pro/wpmcp: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/com.wpmcp-pro/wpmcp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 5 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.wpmcp-pro/wpmcp)](https://protocolprobe.com/mcp/servers/com.wpmcp-pro/wpmcp)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology