autowpmcp

AutoWP MCP Server acts as a bridge between Claude (or other LLM clients) and your WordPress site. It exposes a suite of tools that let the AI authenticate with WordPress, verify connectivity, create and format content, manage categories and tags, and handle media and drafts. By using the MCP interface, you can issue structured tool calls like authenticate-wp, test-wp-connection, create-blog-post, get-wp-categories, get-wp-tags, format-wp-content, and draft-related actions such as save-draft and load-draft. This enables secure, Wi-Fi-friendly automation of common WordPress tasks directly from conversational prompts, while respecting WordPress permissions and site structure.

To use it, configure Claude Desktop (or your MCP client) to point to the autowp MCP server. The typical workflow is to first authenticate to your WordPress site with authenticate-wp, test connectivity with test-wp-connection, and then proceed to create or update posts using create-blog-post. You can fetch available categories and tags with get-wp-categories and get-wp-tags, format content with format-wp-content, and manage media via the media tools like upload-media, list-media, and get-media-details. Drafts can be saved and loaded locally to refine content before publishing.

Prerequisites:

• Node.js and npm installed on your machine
• Access to a WordPress site and an application password or credentials with appropriate permissions
• Optional: Claude Desktop (or other MCP client) for testing

1. Install dependencies and build

git clone <repository-url>
cd autowpmcp
npm install
npm run build

2. Run the MCP server

npm start

3. Configure Claude Desktop MCP integration

In Claude Desktop, add a new MCP server configuration that points to the built MCP entrypoint. Example configuration:

{
  "mcpServers": {
    "autowp": {
      "command": "node",
      "args": ["/path/to/your/autowp-mcp/build/index.js"]
    }
  }
}

4. Provide WordPress credentials securely

• The MCP server expects WordPress site URL, username, and an application password. Populate these in the environment or supply via the CLI as configured by your deployment. See the mcp_config env placeholders for details.

5. Verify setup

• Use the test-wp-connection tool to verify connectivity, then proceed to create a post with create-blog-post and format content with format-wp-content.

Notes and tips:

• Use application passwords from WordPress for authentication (recommended over basic passwords). Ensure the account has appropriate capabilities for the actions you want to perform.
• If your WordPress site uses self-signed certificates, consider configuring WP site URL handling or PEM trust in the environment.
• The MCP server routes commands through the autowp MCP entrypoint; ensure the build output path in the mcp_config matches your deployment.
• For large posts, consider using save-draft to keep local iterations and publish when ready.
• Environment variables can be extended to include site-specific options like default post status (draft/publish) or default category/tags for created posts.