WP Navigator MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WPNAV_BASE | Yes | The WP Navigator API base endpoint (e.g., https://your-site.com/wp-json/wpnav/v1) | |
| WP_APP_PASS | Yes | Your WordPress application password (format: xxxx xxxx xxxx xxxx xxxx xxxx) | |
| WP_APP_USER | Yes | Your WordPress username for application password authentication | |
| WP_BASE_URL | Yes | The base URL of your WordPress site (e.g., https://your-site.com) | |
| WP_REST_API | Yes | The WordPress REST API endpoint (e.g., https://your-site.com/wp-json) | |
| WPNAV_INTROSPECT | Yes | The WP Navigator introspect endpoint (e.g., https://your-site.com/wp-json/wpnav/v1/introspect) | |
| ALLOW_INSECURE_HTTP | No | Allow HTTP for localhost development. Set to 1 to allow insecure connections | 0 |
| WPNAV_ENABLE_WRITES | No | Enable write operations (create/update/delete). Set to 1 to enable, 0 for read-only mode (safe by default) | 0 |
| WPNAV_MAX_RESPONSE_KB | No | Maximum response size in kilobytes before truncation | 64 |
| WPNAV_TOOL_TIMEOUT_MS | No | Per-tool timeout in milliseconds (default: 10 minutes) | 600000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wpnav_introspectA | Get WP Navigator Pro API capabilities, policy configuration, and environment hints. Call this first to understand what the API can do. |
| wpnav_search_toolsA | Find WP Navigator tools by natural language query or category. Returns tool names and brief descriptions only (not full schemas). Use wpnav_describe_tools to get full schemas for tools you want to use. |
| wpnav_describe_toolsA | Get full input schemas for specific WP Navigator tools. Call this after using wpnav_search_tools to get the schemas you need before calling wpnav_execute. |
| wpnav_executeA | Execute any WP Navigator tool by name. Use wpnav_search_tools to discover tools and wpnav_describe_tools to get their schemas first. |
| wpnav_contextA | Get a compact context dump of the WordPress site including focus mode, available tools, active role, cookbooks, site info, and safety settings. Designed for AI agent initialization. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Tools Overview | Categorized list of all available WP Navigator tools with use cases |
| Site Context | Current WordPress site information including theme, plugins, and configuration |
| Guide: Gutenberg | How to build pages with Gutenberg blocks |
| Guide: Workflows | Common workflow patterns for content, plugins, and users |
| Roles List | List of all available AI roles with metadata |
| Cookbooks List | List of all available plugin cookbooks with metadata |
| Role: content-editor | Focuses on content creation and editing for WordPress sites |
| Role: developer | Technical focus for development and debugging tasks |
| Role: seo-specialist | Focuses on search engine optimization and discoverability |
| Role: site-admin | Full administrative access for site management |
| Cookbook: Gutenberg | Best practices for creating and editing content with the WordPress Block Editor (Gutenberg). Use when working with block-based pages and posts. |
| Cookbook: Elementor | Best practices for editing Elementor pages via WP Navigator MCP. Use when working with pages that have data-elementor-type markers or _elementor_data post meta. |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: wpnav_context provides site context for initialization, wpnav_describe_tools gives detailed schemas, wpnav_execute runs tools, wpnav_introspect reveals API capabilities, and wpnav_search_tools finds tools by query. Their descriptions explicitly differentiate their roles and usage sequences.
All tools follow a consistent 'wpnav_' prefix with descriptive snake_case names (e.g., wpnav_context, wpnav_describe_tools). This pattern is uniform across all five tools, making them predictable and easy to identify as part of the same server.
With 5 tools, the count is well-scoped for a WordPress navigation server. Each tool serves a specific function in the workflow (discovery, description, execution, context, and introspection), and none feel redundant or missing for the apparent purpose of managing WordPress tools.
The tool set provides complete coverage for the WordPress navigation domain: wpnav_introspect and wpnav_context handle initialization and understanding, wpnav_search_tools and wpnav_describe_tools cover discovery and schema retrieval, and wpnav_execute enables action. This creates a seamless workflow with no obvious gaps or dead ends.