How do I install Wpagent?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Wpagent need an API key?

The publisher lists these environment variables: WP_SITE_URL, WP_API_KEY_ID, WP_API_SECRET, WP_SITE_LABEL.

What transport does Wpagent use?

Wpagent runs locally over stdio.

When was Wpagent last checked?

Last checked 2026-11-08. Manage WordPress & WooCommerce from any MCP client — 58 tools over a signed REST API.

Wpagent MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y [email protected]

Credentials from the publisher

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

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1WP_SITE_URL=<value> WP_API_KEY_ID=<value> WP_API_SECRET=<secret> WP_SITE_LABEL=<value> claude mcp add dev.wpagent-wpagent-mcp -- npx -y wpagent-mcp@1.1.4

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "dev.wpagent-wpagent-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ],9      "env": {10        "WP_SITE_URL": "<value>",11        "WP_API_KEY_ID": "<value>",12        "WP_API_SECRET": "<secret>",13        "WP_SITE_LABEL": "<value>"14      }15    }16  }17}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 1.1.4

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

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:

{
  "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

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.

Wpagent

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Wpagent?

Does Wpagent need an API key?

What transport does Wpagent use?

When was Wpagent last checked?

Documentation

wpagent-mcp

Install

Environment variables

What it can do

What it will not do

Safety

Related

Licence