Labsco
diazoxide logo

WordPress Standalone

β˜… 8

from diazoxide

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

πŸ”₯πŸ”₯πŸ”₯πŸ”₯βœ“ VerifiedFreeQuick setup

MseeP.ai Security Assessment Badge

WordPress Standalone MCP Server

A powerful Model 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.

✨ Features

  • πŸ”„ 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

Tools Reference

Dynamic Endpoint Tools

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]_id for ID-specific endpoints.

Examples:

  • 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

wp_discover_endpoints

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

Arguments:

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

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

πŸ› οΈ Generated Tools

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

Discovery Tool

  • wp_discover_endpoints - Re-discover available endpoints for a site

πŸ—οΈ Architecture

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚   Claude AI     β”‚    β”‚  MCP Server      β”‚    β”‚  WordPress API  β”‚
β”‚                 │◄──►│                  │◄──►│                 β”‚
β”‚ Natural Languageβ”‚    β”‚ Dynamic Tools    β”‚    β”‚ REST Endpoints  β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜    β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜    β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                              β”‚
                              β–Ό
                       β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                       β”‚  Configuration   β”‚
                       β”‚   wp-sites.json  β”‚
                       β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

πŸ”’ Security

  • 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

🀝 Contributing

We welcome contributions! Please see our Contributing Guide for details.

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Add tests if applicable
  5. Submit a pull request

πŸ“„ License

MIT License - see LICENSE file for details.

πŸ™ Acknowledgments

  • 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