English Français العربية

dev.wpagent/wpagent-mcp

Official registry E-commerce

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

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package wpagent-mcp
Claude Code 
claude mcp add wpagent-mcp -e 'WP_SITE_URL=<WP_SITE_URL>' -e 'WP_API_KEY_ID=<WP_API_KEY_ID>' -e 'WP_API_SECRET=<your wp_api_secret>' -e 'WP_SITE_LABEL=<WP_SITE_LABEL>' -- npx -y wpagent-mcp@1.1.4
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "wpagent-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "wpagent-mcp@1.1.4"
            ],
            "env": {
                "WP_SITE_URL": "<WP_SITE_URL>",
                "WP_API_KEY_ID": "<WP_API_KEY_ID>",
                "WP_API_SECRET": "<your wp_api_secret>",
                "WP_SITE_LABEL": "<WP_SITE_LABEL>"
            }
        }
    }
}

Environment variables

  • WP_SITE_URL required Base URL of your WordPress site, no trailing slash
  • WP_API_KEY_ID required API key id shown by the WpAgent plugin
  • WP_API_SECRET required secret API key secret, displayed once at generation
  • WP_SITE_LABEL Friendly name for the site; defaults to the hostname

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. wpagent-mcp
  2. Install
  3. What it can do
  4. What it will not do
  5. Safety
  6. Related
  7. Licence

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.

  1. Install the WpAgent plugin on your WordPress site and activate it.
  2. 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.
  3. Add the server to your MCP client. For Claude Desktop, in claude_desktop_config.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"
      }
    }
  }
}

For Claude Code:

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
VariableRequiredWhat it is
WP_SITE_URLyesYour site's base URL, no trailing slash
WP_API_KEY_IDyesThe key id shown in the plugin
WP_API_SECRETyesThe secret, displayed once at generation
WP_SITE_LABELnoA friendly name; defaults to the hostname

What it can do

AreaExamples
Pluginslist, search wordpress.org, install, activate, deactivate, update, delete
Contentposts, pages, products, any custom post type, with meta and featured images
Themeslist, search, install, activate, theme mods, custom CSS, logo, colours
WooCommercesettings, orders, coupons, shipping zones, payment gateways, tax rates, stats
Structuremenus, widgets, sidebars, taxonomies, terms, redirections
Mediabrowse, upload, delete
Users & commentslist, create, update, moderate
Auditbest-practices check over security, SEO, performance, with auto-fixes
WP-CLIallowlisted 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

Frequently asked questions

What is dev.wpagent/wpagent-mcp?

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

How do I install dev.wpagent/wpagent-mcp?

It runs on your machine. In Claude Code: claude mcp add wpagent-mcp -e 'WP_SITE_URL=<WP_SITE_URL>' -e 'WP_API_KEY_ID=<WP_API_KEY_ID>' -e 'WP_API_SECRET=<your wp_api_secret>' -e 'WP_SITE_LABEL=<WP_SITE_LABEL>' -- npx -y wpagent-mcp@1.1.4. For other clients, paste the JSON configuration from this page into their MCP settings.

Does dev.wpagent/wpagent-mcp need an API key?

Yes. It expects WP_SITE_URL, WP_API_KEY_ID, WP_API_SECRET, which you set in its configuration.

Is dev.wpagent/wpagent-mcp open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains dev.wpagent/wpagent-mcp?

It is published by THE-KIPDEV. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.