About this integration
MCP server for WordPress. Manage posts, users, comments, terms, metadata, and settings.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 1.0.9
- Package
- @rnaga/wp-mcp
- Last compatibility test
- Not independently tested
Connect your agent
@rnaga/wp-mcpReview is limited to the documented local STDIO artifact already represented by the existing listing. The separately documented HTTP and proxy modes have different connection and interactive authorization requirements and are not projected here. No package, database, or WordPress site was executed.
Capabilities: Manage WordPress posts and revisions, Moderate comments, Manage users subject to WordPress capabilities, Manage terms and metadata, Manage WordPress settings and options
Connected profiles
Additional details
io.github.rnaga/wp-mcp
Source ↗ · Checked 2026-09-171.0.9
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17LOCAL_USERNAME, WP_DB_HOST, WP_DB_NAME, WP_DB_USER, WP_DB_PASSWORD
Source ↗ · Checked 2026-09-17@rnaga/wp-mcp
Source ↗ · Checked 2026-09-191.0.9
Source ↗ · Checked 2026-09-19After one-time database configuration, the MCP client launches the local server process and the secret store loads its connection values before local start.
Source ↗ · Checked 2026-09-19The local mode uses database host, database name, user, password, optional TLS files, and a WordPress username whose roles control available tools. This database-and-assumed-user mechanism is not one of the native authentication taxonomy values.
Source ↗ · Checked 2026-09-19The documented client configuration launches npx -y @rnaga/wp-mcp -- local start over stdio and connects directly to the configured WordPress database.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19