
Mcpwp
io.github.mumega848Published by GitHub account mumega848v3.0.1Updated Oct 24, 2026
MCP for WordPress — connect Claude, Cursor, or Windsurf to any WordPress site.
Overview
Connects an AI assistant to a WordPress site so it can work with that site's content through the MCPWP plugin.
- What you can do
- MCPWP is a local MCP server that links an AI assistant such as Claude, Cursor, or Windsurf to a WordPress site. It runs over stdio and authenticates to the site using an MCPWP API key generated in the WordPress admin. The registry description states its purpose is connecting assistants to any WordPress site; no individual tools are listed in the supplied manifest.
- When to use it
- Worth adding when you want an assistant to operate on a specific WordPress installation rather than generic web content, for example drafting, editing, or managing site content from your editor or chat client. It suits users who already run WordPress and can install the MCPWP plugin and issue an API key.
- Requirements
- Runs as a local process on the user's machine, installed from the npm package @mcpwp.net/mcpwp over stdio; desktop only, not web-executable. Requires the WP_URL environment variable with the WordPress site URL and the WP_API_KEY secret, generated in WP Admin under MCPWP then Setup. Network access to that WordPress site is needed.
Installation
In SourceWeft
- Open Mcpwp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v3.0.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.