WordPress MCP Server A Model Context Protocol (MCP) server that provides direct access to the WordPress REST API — allowing LLMs, agents, and automation tools to perform structured actions such as publishing posts, fetching content, managing media, or retrieving site data. This server runs on Apify as a standby actor, meaning it only activates when invoked via an MCP client. It authenticates securely using WordPress Application Passwords and an Apify token passed in the URL query string. For more details about MCP and how to connect servers, visit mcp.apify.com. --- ## 🌐 Connection URL Connect to this MCP server at: text https://extremescrapes--wordpress-mcp-server.apify.actor/mcp?token=apify_api_yourtokenhere > ⚠️ Important: > Replace apify_api_yourtokenhere with your personal Apify API token, which you can find under > Apify Console → Integrations. > > The token must be appended as a query parameter (?token=...) — header-based authorization is not used. --- ## ⚙️ Client Configuration To connect using an MCP-compatible client (like MCP Inspector or LM Studio), use: json { "servers": { "wordpress": { "url": "https://extremescrapes--wordpress-mcp-server.apify.actor/mcp?token=apify_api_yourtokenhere", "headers": { "x-wp-url": "https://yourwordpresssite.com", "x-wp-username": "your_wp_username", "x-wp-password": "your_wp_app_password" } } } } > Note: > > * No Authorization header is required. > * The token must be included in the URL query string. > * WordPress credentials are passed as headers: > > * x-wp-url: Your WordPress base URL (e.g., https://example.com) > * x-wp-username: Your WordPress username > * x-wp-password: Your WordPress Application Password All credentials are used in-memory only — they are never stored or logged. --- ## 🔒 Authentication This server uses two authentication layers: 1. Apify Token (via URL) * Required to activate the standby actor. * Example: https://extremescrapes--wordpress-mcp-server.apify.actor/mcp?token=apify_api_wLcRks0Rh6E5jCusmirDrhX7sYwvYM2ICXPM * You can generate or view your token in your Apify account settings. 2. WordPress Application Passwords * Used to securely authenticate with your WordPress REST API. * Generate under: Dashboard → Users → Profile → Application Passwords --- ## 🧠 Available Tools The WordPress MCP Server exposes a structured set of tools (actions) that correspond to standard WordPress REST API endpoints.

Content Management

* wp_list_posts * Fetch a paginated list of posts. * Parameters: * status (string, optional): Filter (publish, draft, etc.) * per_page (number, optional): Posts per page * page (number, optional): Page number * wp_create_post * Create and publish a new post. * Parameters: * title (string): Post title * content (string): Post content * status (string, optional): Post status (publish, draft, etc.) * featured_media_url (string, optional): URL of featured image * wp_update_post * Update an existing post by ID. * Parameters: * id (number): Post ID * title (optional): New title * content (optional): Updated content * status (optional): New status * wp_delete_post * Delete a post permanently. * Parameters: * id (number): Post ID

Media Management

* wp_upload_media * Upload an image or file to the WordPress Media Library. * Parameters: * url (string): Direct media file URL

Site Information

* wp_get_site_info * Retrieve general WordPress site metadata such as name, URL, and timezone. * Parameters: None

--- ## 🧩 Example Usage Once connected to this MCP server, your LLM or MCP-compatible client (like ChatGPT, Claude, or MCP Inspector) can directly call WordPress actions through structured tool invocations. For example, in a chat with an LLM that has this server configured, you can simply say: > User: Create a new post on my WordPress site titled “Hello from MCP” with the content “This post was published automatically via the WordPress MCP Server.” The LLM will automatically invoke the wp_create_post tool behind the scenes, using your configured credentials and Apify token. --- ## 🧭 Links * Actor Page: https://apify.com/extremescrapes/wordpress-mcp-server * WordPress REST API Docs: https://developer.wordpress.org/rest-api/reference/ * Apify MCP Docs: https://mcp.apify.com --- ## ⚡ Key Features * 🔗 Seamless connection to the WordPress REST API * 🧱 100% MCP-compatible for LLM and agent integrations * 🔐 Dual authentication (Apify token + WordPress Application Password) * 💤 Hosted as a standby actor — runs only when invoked * 🌍 Works with any WordPress installation that supports Application Passwords * ⚙️ Lightweight and stateless — no data persistence --- ## 💡 Use Cases * ✍️ AI-Powered Blogging: Automatically generate and publish blog posts from GPT or other LLMs. * 📰 Automated News Aggregation: Fetch and publish daily news summaries to your WordPress site. * 🖼️ Media Library Automation: Auto-upload featured images or assets from URLs or AI-generated sources. * 🧾 Bulk Post Management: Use structured MCP workflows to edit, republish, or delete posts at scale. * 🤖 Agent-Based Publishing: Allow AI agents to directly manage WordPress sites via the REST API. * 📅 Automated Scheduling: Queue posts based on time, topic, or content category. * 🧠 Knowledge Base Creation: Let LLMs populate a WordPress wiki or documentation site programmatically. * 📈 Cross-Platform Content Sync: Mirror or syndicate content from Notion, Substack, or Medium into WordPress. * 💬 Comment Moderation & Insights: Fetch, analyze, and summarize comments using LLMs for moderation or analytics. * 🔍 AI Search Indexing: Query and structure WordPress posts for semantic search or recommendation systems. --- This WordPress MCP Server bridges your WordPress site with the modern MCP ecosystem — making it effortless for AI systems, autonomous agents, or other services to manage and create content dynamically. ---