Wpagent Mcp

dev.wpagentPublished by wpagent.devv1.1.4Updated Oct 26, 2026

Manage WordPress & WooCommerce from any MCP client — 58 tools over a signed REST API.

VerifiedSTDIODesktop onlyDeveloper Tools Business & Commerce

Server details

Identifier: dev.wpagent/wpagent-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to wpagent.dev. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/dev.wpagent%2Fwpagent-mcp.svg)](https://sourceweft.com/mcp/dev.wpagent%2Fwpagent-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Lets an MCP client operate a WordPress and WooCommerce site — plugins, content, themes, media, users and orders — through a signed REST bridge.

What you can do: Manage plugins and themes: list, search wordpress.org, install, activate, deactivate, update, delete, edit theme mods and custom CSS
Create and edit content: posts, pages, products, custom post types, with meta and featured images
Handle WooCommerce: settings, orders, coupons, shipping zones, payment gateways, tax rates and stats
Organize site structure: menus, widgets, sidebars, taxonomies, terms and redirections
Browse, upload and delete media; list, create, update and moderate users and comments
Run a best-practices audit over security, SEO and performance with auto-fixes, and allowlisted WP-CLI commands when enabled
When to use it: Useful when you want an assistant to make real changes on a self-hosted WordPress or WooCommerce site — publishing content, installing plugins, adjusting store settings — instead of just drafting text for you to paste in.
Requirements: Runs locally via npx (Node.js) over stdio. Needs the free WpAgent plugin installed and activated on the WordPress site, plus an API key generated there. Required environment variables: WP_SITE_URL, WP_API_KEY_ID and WP_API_SECRET; WP_SITE_LABEL is optional. The client must reach the site directly over the network.

Before you install

The key's permissions decide what the assistant can do, and it can delete content, plugins, media and users, so a read-only key is a safer start and a current backup is advised. WP_API_SECRET is shown only once at generation and should be kept private. WP-CLI stays off unless the site owner enables it in wp-config.php. Every call is logged in the WordPress admin and keys can be revoked there.

Installation

In SourceWeft

Open Wpagent Mcp 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

wpagent-mcp

An MCP server that lets Claude — or any MCP-compatible client — actually operate a WordPress site: plugins, content, themes, menus, media, users, WooCommerce, Elementor and WP-CLI.

It talks to your site through the free WpAgent bridge plugin over a REST API where every request is signed with HMAC-SHA256. No site credentials are involved, and no data passes through a third-party service: the connection is client → your WordPress, directly.

Install

Nothing to install ahead of time — the config below fetches it on demand.

Install the WpAgent plugin on your WordPress site and activate it.
In the WordPress admin, open WpAgent and generate an API key. Choose the permissions you want the assistant to have; a read-only key is a sound way to start.
Add the server to your MCP client. For Claude Desktop, in claude_desktop_config.json:

json

{  "mcpServers": {    "wpagent": {      "command": "npx",      "args": ["-y", "wpagent-mcp"],      "env": {        "WP_SITE_URL": "https://your-site.com",        "WP_API_KEY_ID": "wpaia_xxxxxxxxxxxx",        "WP_API_SECRET": "the secret shown once when you generated the key"      }    }  }}

{  "mcpServers": {    "wpagent": {      "command": "npx",      "args": ["-y", "wpagent-mcp"],      "env": {        "WP_SITE_URL": "https://your-site.com",        "WP_API_KEY_ID": "wpaia_xxxxxxxxxxxx",        "WP_API_SECRET": "the secret shown once when you generated the key"      }    }  }}

For Claude Code:

bash

claude mcp add wpagent \  --env WP_SITE_URL=https://your-site.com \  --env WP_API_KEY_ID=wpaia_xxxxxxxxxxxx \  --env WP_API_SECRET=... \  -- npx -y wpagent-mcp

claude mcp add wpagent \  --env WP_SITE_URL=https://your-site.com \  --env WP_API_KEY_ID=wpaia_xxxxxxxxxxxx \  --env WP_API_SECRET=... \  -- npx -y wpagent-mcp

Environment variables

Variable	Required	What it is
`WP_SITE_URL`	yes	Your site's base URL, no trailing slash
`WP_API_KEY_ID`	yes	The key id shown in the plugin
`WP_API_SECRET`	yes	The secret, displayed once at generation
`WP_SITE_LABEL`	no	A friendly name; defaults to the hostname

What it can do

Area	Examples
Plugins	list, search wordpress.org, install, activate, deactivate, update, delete
Content	posts, pages, products, any custom post type, with meta and featured images
Themes	list, search, install, activate, theme mods, custom CSS, logo, colours
WooCommerce	settings, orders, coupons, shipping zones, payment gateways, tax rates, stats
Structure	menus, widgets, sidebars, taxonomies, terms, redirections
Media	browse, upload, delete
Users & comments	list, create, update, moderate
Audit	best-practices check over security, SEO, performance, with auto-fixes
WP-CLI	allowlisted commands, off unless enabled in `wp-config.php`

What it will not do

The API has no path to arbitrary PHP, no path to your database, and no path to wp-config.php. WP-CLI execution is disabled unless the site owner adds define('WPAIA_ENABLE_WPCLI', true); on the server, and even then only allowlisted commands run — db, eval, eval-file, shell, server, config and package are always refused.

Safety

Every request is signed with HMAC-SHA256 and carries a timestamp; requests older than five minutes are rejected.
Permissions are per key and checked on every route, so a read-only key stays read-only.
Every call is written to an audit log you can read in the WordPress admin.
Revoking a key in WordPress takes effect immediately.

Ask the assistant to confirm before destructive actions, and keep a current backup — it can delete content when you tell it to.

WpAgent — hosted dashboard built on the same bridge, with a free read-only tier
The bridge plugin is GPL-2.0-or-later; this server is MIT.

Licence

MIT © KipDev

Source: README.md at commit 9e7ef03

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.1.4LatestSep 16, 2026

Score

50% 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
License10 pts