WordPress MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 24 Oct 2026.
Publish and manage WordPress pages, posts, media
We read the source, 1 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
cacheFile := filepath.Join(c.cacheDir, c.cacheKey(path, params)+".json")
select {
case <-time.After(interval + jitter):
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Schedule, publish and manage social media posts across platforms.
WordPress MCP server: publish posts, AI images, SEO and full site management, self-hosted
MCP server for WordPress. Manage posts, users, comments, terms, metadata, and settings.
Search, read and publish X posts and manage users, lists and media via the X API v2.
Publish, schedule, and manage social media posts across major platforms via the Postproxy API.
Manage BrightSite websites: pages, blog posts, components, forms, media, and analytics.
Create, edit and publish micropage.sh landing pages and blog posts from markup.
Publish to self-hosted WordPress from AI agents: markdown, images, SEO, and Notion sync.
Answers built from our own checks of this server.