- Home
- MCP servers
- WP Navigator
WP Navigator
- typescript
0
GitHub Stars
typescript
Language
7 months ago
First Indexed
3 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"littlebearapps-wp-navigator-mcp": {
"command": "npx",
"args": [
"-y",
"@littlebearapps/wp-navigator-mcp",
"./wpnav.config.json"
],
"env": {
"ALLOW_INSECURE_HTTP": "1",
"WPNAV_ENABLE_WRITES": "1"
}
}
}
}WP Navigator MCP provides an extensible bridge between AI assistants and WordPress, enabling safe-by-default content and site management actions with full rollback support. You can perform posts, media, plugins, themes, and Gutenberg block edits through natural language while enforcing granular permissions and secure connections.
How to use
You access WordPress management through an MCP client that speaks the MCP protocol to the WP Navigator MCP server. Start by enabling read-only operations by default, then opt in to create/update/delete actions when you are ready. You can perform actions such as creating posts with Gutenberg blocks, uploading media from URLs, managing plugins and themes, and inspecting site status. All changes are tracked with full revision history and rollback capability.
How to install
Prerequisites: you need Node.js and npm installed on your machine, and access to a WordPress site with the WP Navigator plugin installed and activated.
Step 1. Install the WP Navigator MCP client configuration in your project.
Step 2. Create your WordPress connection and MCP manifest in your project as shown below.
Configuration and usage notes
Create an application password in WordPress so the MCP client can authenticate. Enable write operations only when you intend to perform create/update/delete actions. Maintain a clear revision history to rollback any unintended changes.
If you are developing locally, you can allow HTTP for localhost development by enabling an insecure HTTP flag in your environment or MCP config.
Configuration example for Claude Code MCP client
{
"mcpServers": {
"wpnav": {
"command": "npx",
"args": ["-y", "@littlebearapps/wp-navigator-mcp", "./wpnav.config.json"],
"env": {
"WPNAV_ENABLE_WRITES": "1"
}
}
}
}
Verification steps
In the Claude Code interface, ask to introspect the WordPress connection or run a simple read query to verify that the MCP server can reach your WordPress site and that the plugin is active.
Additional sections
This MCP server supports safe-by-default writes, full revision history, policy-based access, and HTTPS enforcement for non-localhost connections. When you want to perform write actions, set WPNAV_ENABLE_WRITES to 1 in your environment or configuration. If something goes wrong, you can use the built-in repair workflow to validate and regenerate configuration.
Available tools
wpnav_introspect
Check the WordPress connection and plugin edition to verify the MCP setup.
wpnav_get_site_overview
Retrieve a high-level overview of the WordPress site, including site health and configuration.
wpnav_list_posts
List posts with optional limits and filters.
wpnav_upload_media_from_url
Upload media directly from a URL and add to the media library.
wpnav_activate_plugin
Activate a WordPress plugin by slug.
wpnav_list_themes
List and manage available WordPress themes.
wpnav_list_users
List WordPress users and their roles.
wpnav_list_comments
List comments and perform moderation actions.
wpnav_batch_get
Retrieve multiple resources in a single call.
wpnav_load_role
Load AI roles for guiding behavior during interactions.