WordPress Standalone

by diazoxide

Not rated
GitHub

About

Integrates AI assistants with WordPress sites using the WordPress REST API.

Details

Author
diazoxide
Categories
Developer Tools, Other, API

Setup

Install WordPress Standalone in your MCP client (Claude Desktop, Cursor, Windsurf, and others).

Repository: https://github.com/diazoxide/wp-standalone-mcp

Follow the installation instructions in the repository README, then restart your MCP client.

Integrates AI assistants with WordPress sites using the WordPress REST API.

A powerfulModel Context Protocol (MCP)server that provides seamless integration between AI assistants and WordPress sites through the WordPress REST API. This server automatically discovers and creates individual tools for each WordPress REST API endpoint, enabling natural language WordPress management.

- πŸ”„ Dynamic Tool Generation: Automatically creates individual tools for each discovered WordPress REST API endpoint
- 🌐 Multi-Site Support: Manage multiple WordPress sites simultaneously from a single configuration
- πŸ”’ Secure Authentication: Uses WordPress Application Passwords for secure API access
- 🎯 Smart Tool Filtering: Include/exclude specific tools using exact match or regex patterns
- πŸ“Š Comprehensive Coverage: Support for posts, pages, users, media, comments, plugins, themes, and more
- πŸš€ Zero Configuration Discovery: Automatically maps all available endpoints without manual setup
- ⚑ High Performance: Efficient endpoint discovery and request handling
- πŸ›‘οΈ Error Handling: Graceful error handling with detailed diagnostic messages

# Install globally npm install -g wp-standalone-mcp # Or run directly with npx npx github:diazoxide/wp-standalone-mcp start

- Create a WordPress Application Password:

- Go to your WordPress admin β†’ Users β†’ Profile

- Scroll to "Application Passwords" section
- Create a new application password
- Copy the generated password

{ "myblog": { "URL": "https://myblog.com", "USER": "your_username", "PASS": "your_application_password" } }
{ "mcpServers": { "wordpress": { "command": "npx", "args": ["-y", "github:diazoxide/wp-standalone-mcp", "start"], "env": { "WP_SITES_PATH": "/absolute/path/to/wp-sites.json" } } } }

When the server starts, it automatically discovers all available WordPress REST API endpoints and creates individual tools for each endpoint/method combination. Tool names follow the pattern:[site]_[method]_[resource]or[site]_[method]_[resource]_idfor ID-specific endpoints.

- myblog_get_v2_posts- List all posts
- myblog_get_v2_posts_id- Get a specific post by ID
- myblog_post_v2_posts- Create a new post
- myblog_put_v2_posts_id- Update a specific post
- myblog_delete_v2_posts_id- Delete a specific post

Re-discovers all available REST API endpoints on a WordPress site.

{ "site": { "type": "string", "description": "Site alias (as defined in configuration)", "required": true } }

Returns:List of available endpoints with their methods and namespaces.

- WP_SITES_PATH: Path to your WordPress sites configuration file
- WP_SITES: Direct JSON configuration (alternative to file)

{ "site_alias": { "URL": "https://your-site.com", "USER": "wordpress_username", "PASS": "application_password", "FILTERS": { "include": ["tool_name_patterns"], "exclude": ["tool_name_patterns"] } } }

- Log in to your WordPress admin dashboard
- Go to Users β†’ Profile
- Scroll to the "Application Passwords" section
- Enter a name for the application (e.g., "MCP Server")
- Click "Add New Application Password"
- Copy the generated password (you won't be able to see it again)

Note: Application Passwords require WordPress 5.6 or later and HTTPS.

Control which WordPress operations are available by filtering tools:

{ "myblog": { "URL": "https://myblog.com", "USER": "admin", "PASS": "abcd 1234 efgh 5678", "FILTERS": { "include": [ "myblog_get_v2_posts", "myblog_post_v2_posts", "/._get_._posts./" ], "exclude": [ "myblog_delete_v2_posts_id", "/._._users./", "/._delete_./" ] } } }

- include: Only specified tools are exposed (whitelist)
- exclude: Specified tools are hidden (blacklist)
- includetakes precedence overexclude
- Supports exact matches and regex patterns (wrap in/pattern/)

The server automatically creates tools following this naming convention:

- Pattern:[site]_[method]_[resource]or[site]_[method]_[resource]_id
- Examples:

- myblog_get_v2_posts- List all posts

- myblog_get_v2_posts_id- Get specific post by ID
- myblog_post_v2_posts- Create new post
- myblog_put_v2_posts_id- Update specific post
- myblog_delete_v2_posts_id- Delete specific post
- myblog_get_v2_media- List media files
- myblog_get_v2_users- List users

- wp_discover_endpoints- Re-discover available endpoints for a site

Once configured, interact with your WordPress sites using natural language:

Can you show me all posts from myblog published in the last month?
Find all posts on testsite tagged with "technology" and "AI"
Show me draft posts from myblog that need review
Create a new draft post on testsite titled "The Future of AI" with these key points: [points]
Update the featured image on myblog's latest post about machine learning
Add a new category called "Tech News" to myblog
Show me all pending comments on myblog's latest post
Find comments from testsite that might be spam
List the most engaged commenters on myblog
What plugins are currently active on myblog?
Check if any plugins on testsite need updates
Tell me about the security plugins installed on myblog
"Show me the last 5 posts from myblog" "Create a new draft post titled 'AI and the Future' on myblog" "Update the featured image for post ID 123 on myblog" "Delete the post with ID 456 from myblog"
"List all images uploaded this month to myblog" "Upload a new image to myblog media library" "Get details for media file ID 789"
"Show all users with editor role on myblog" "Create a new contributor account on myblog" "Update user permissions for user ID 101"
"What plugins are active on myblog?" "Show me all pending comments" "Get the current theme information" "List all categories and their post counts"
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ Claude AI β”‚ β”‚ MCP Server β”‚ β”‚ WordPress API β”‚ β”‚ │◄──►│ │◄──►│ β”‚ β”‚ Natural Languageβ”‚ β”‚ Dynamic Tools β”‚ β”‚ REST Endpoints β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚ β–Ό β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ Configuration β”‚ β”‚ wp-sites.json β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

- Application Passwords: Uses WordPress's secure application password system
- HTTPS Required: All connections must use HTTPS
- Configuration Security: Keep configuration files outside web-accessible directories
- Principle of Least Privilege: Use accounts with minimal required permissions
- No Credential Storage: Credentials are only used for API authentication

- Verify site alias in configuration matches usage
- Check configuration file path and format

- Verify application password is correct
- Ensure user account has necessary permissions
- Check if site URL is accessible

- Verify WordPress site has REST API enabled
- Check if site URL includes/wp-jsonaccessibility
- Review any security plugins blocking REST API

SetDEBUG=wp-mcpenvironment variable for detailed logging:

DEBUG=wp-mcp npx github:diazoxide/wp-standalone-mcp start

- WordPress: 5.6+ (for Application Passwords)
- Node.js: 16+
- HTTPS: Required for Application Passwords
- REST API: Must be enabled (default in WordPress)

We welcome contributions! Please see ourContributing Guidefor details.
- Fork the repository
- Create a feature branch
- Make your changes
- Add tests if applicable
- Submit a pull request

MIT License - seeLICENSEfile for details.

- Repository:https://github.com/diazoxide/wp-standalone-mcp
- Issues:
https://github.com/diazoxide/wp-standalone-mcp/issues
- WordPress REST API:
https://developer.wordpress.org/rest-api/
- Model Context Protocol:
https://modelcontextprotocol.io/

- WordPress REST API team for the comprehensive API
- Anthropic for the Model Context Protocol specification
- The open-source community for continuous support and feedback

Made with ❀️ for the WordPress and AI community

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Interact with WordPress sites via the REST API. Manage content, posts, and site configurations for multiple sites using natural language.

Manage WordPress sites via the REST API. Enables AI assistants to handle content, posts, and site configurations.

Manage and utilize website content within the DevHub CMS platform

A server for integrating with WordPress sites, enabling content management and interaction via the Model Context Protocol.

An MCP server for WordPress and Elementor, enabling AI assistants to manage content and build pages.

Model Context Protocol (MCP) server for Kinsta WordPress hosting

Manage WordPress posts and upload images directly from file paths.

A server for integrating with the WordPress REST API.

A comprehensive MCP server for managing WordPress sites, featuring a wide range of tools for performance monitoring, caching, and more.

No reviews yet β€” be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.