This MCP server exposes a WordPress API integration, allowing an AI assistant to manage posts, users, comments, and taxonomies via the WordPress REST API. The available tools cover core CMS tasks such as creating, fetching, updating, and deleting posts; retrieving and managing users and comments; handling categories and tags; and executing custom REST API requests. To use it, point the MCP client at the server (configured with your WordPress site URL and credentials) and invoke the provided tools with the required parameters. Each tool requires siteUrl, username, and password for authentication, plus resource-specific fields like postId, title, content, or custom data as needed. For security, prefer using WordPress application passwords and avoid embedding credentials directly in prompts; instead, leverage the server’s authentication flow where possible.

The server supports the following tool domains: Post Management (create_post, get_posts, update_post, delete_post), User Management (get_users, get_user, get_user_by_login), Comment Management (get_comments, create_comment), Category and Tag Management (get_categories, create_category), and Custom Requests (custom_request) to interact with any WordPress REST API endpoint. Each tool returns data from WordPress so you can chain results to drive more advanced workflows (e.g., fetch posts, then update a selected one, or create a comment on a specific post).

Prerequisites:

• Node.js v18 or higher
• npm (bundled with Node.js) or yarn
• A WordPress site with REST API enabled and a WordPress application password for authentication

Installation steps:

1. Clone the repository: git clone <repository-url> cd wordpress-mcp-server

2. Install dependencies: npm install

3. Build the server (if there is a build step): npm run build

4. Run the MCP server (example):

   Depending on your setup, point to the built entrypoint

   node path/to/wordpress-mcp-server/build/index.js

5. Configure MCP settings: Update your MCP settings file (e.g., settings/cline_mcp_settings.json) to include the wordpress server entry, for example: { "mcpServers": { "wordpress": { "command": "node", "args": ["path/to/wordpress-mcp-server/build/index.js"] } } }

6. Provide credentials securely: Ensure WP_SITE_URL, WP_USERNAME, and WP_PASSWORD (application password) are available to the server via environment variables or a secure secrets store as configured in your deployment.

7. Test the setup: Use the MCP client to call tools like create_post or get_posts and verify responses from your WordPress site.

Tips and common issues:

• Ensure WordPress REST API is enabled (default in WordPress 4.7+).
• Use WordPress application passwords for authentication; do not reuse admin credentials.
• If you encounter CORS or network errors, verify that the WordPress site URL configured in the environment variables is correct and accessible from the MCP server environment.
• When using custom_request, provide a valid endpoint and method; test with a simple GET endpoint first to validate connectivity.
• For large post listings, adjust perPage and page parameters to manage pagination effectively.
• If npm run build is not defined in your package, skip to the direct run step using the built file path.
• Securely manage your credentials; avoid committing credentials in code or settings files.