Creativity · MCP — server
MCP WordPress Server
The MCP WordPress Server is a community-maintained Model Context Protocol server wrapping the WordPress REST API. Authenticated with application passwords or WP.com OAuth, it lets an LLM client list and draft posts, upload media, manage categories, and update metadata — giving editors an AI copilot inside their existing site.
MCP facts
- Kind
- server
- Ecosystem
- anthropic-mcp
- Language
- Python
- Transports
- stdio
Capabilities
- Tools: list_posts, create_post, update_post, upload_media, list_categories
- Resources: wp://post/{id} and wp://media/{id} URIs
- Auth: WP_URL + WP_USERNAME + WP_APP_PASSWORD env vars
Install
pip install mcp-server-wordpress && python -m mcp_server_wordpress Configuration
{
"mcpServers": {
"wordpress": {
"command": "python",
"args": ["-m", "mcp_server_wordpress"],
"env": {
"WP_URL": "https://blog.example.com/wp-json",
"WP_USERNAME": "editor",
"WP_APP_PASSWORD": "xxxx xxxx xxxx xxxx"
}
}
}
} Frequently asked questions
Is this server official?
No — it is community-maintained. Automattic has released exploratory MCP demos, but production servers today are community wrappers around REST API v2.
What are application passwords?
WordPress core supports per-user 'application passwords' generated from the Users > Profile page. They are the safest auth option for REST API integrations.
Does it work with custom post types?
Yes, if the CPT is exposed via the REST API (show_in_rest: true). Most community servers accept a custom post-type slug parameter on the list and create tools.
Sources
- WordPress REST API handbook — accessed 2026-04-20
- MCP community servers — accessed 2026-04-20