Mordenhost MCP

Give AI assistants a safe, authenticated way into WordPress.
Self-hosted OAuth and API keys, per-tool capability checks, audit logging, and 111 always-on tools plus opt-in integrations.

Mordenhost MCP is a self-hosted Model Context Protocol server built into WordPress by Mordenhost. Claude, ChatGPT, Gemini, AI coding assistants, and any other MCP-compatible agent operate your site through typed, permission-checked tools — no screen scraping, no browser automation, no copy-paste.

Where a bare MCP bridge stops at exposing functions, Mordenhost MCP is built for sites that are actually in production. Every request authenticates through OAuth 2.0 or an API key, hits a per-IP rate limit, and passes a WordPress capability check inside the tool handler before it touches anything. Interactions are logged for audit — tool names and argument keys, never the argument values. Nothing leaves your database: no license server, no telemetry, no callback to Mordenhost or anyone else.

A standard installation exposes 111 always-on tools for WordPress core, Gutenberg blocks, and outbound webhooks. Compatible plugins can add specialized tools once an administrator enables their integration, while eleven high-impact plugin and theme lifecycle tools remain disabled until an administrator explicitly enables them. The live count depends on the active integrations and permissions and is shown in the Documentation panel, which reads the registry directly; every tool is reachable through the native MCP endpoint, the classic REST API, and the WordPress Abilities API on WordPress 6.9 or later.

Contents

• How it works
• Requirements
• Installation
• Tool inventory
• Plugin integrations
• Supported clients and platforms
• Security and privacy
• Frequently asked questions
• License

How it works

flowchart LR
    C["MCP clients"] --> M["Streamable HTTP MCP endpoint"]
    O["OAuth 2.0"] --> M
    K["Mordenhost MCP API key"] --> M
    R["REST clients"] --> API["Classic REST API"]
    A["WordPress 6.9+ consumers"] --> AB["Abilities API"]
    M --> G["Authentication, rate limiting, and origin checks"]
    G --> T["Shared tool registry and handlers"]
    API --> T
    AB --> T
    T --> P["WordPress capability checks"]
    P --> W["WordPress core and Gutenberg APIs"]
    P --> I["Detected plugin integrations"]

All three public tool surfaces route into the same registry and handlers, so capability checks and tool behavior remain consistent. The primary endpoint is:

https://yoursite.com/wp-json/mordenhost-mcp/v1/mcp

OAuth discovery and authorization endpoints live at the domain root.

Why security matters

MCP tools can read, create, update, and delete WordPress data. Mordenhost MCP protects that access with:

• OAuth 2.0 authorization code flow with PKCE and refresh-token rotation.
• Static API-key authentication for clients that do not support OAuth.
• Timing-safe credential comparison and authenticated session initialization.
• Origin validation and per-IP rate limiting of 60 requests per minute.
• WordPress capability checks inside every tool handler.
• Audit logging that records tool names and argument keys, never argument values.
• Read-after-write verification for mutation tools.
• Dry-run, confirmation, guard, and undo mechanisms on supported high-impact operations.
• Cache-Control: no-store across the Mordenhost MCP namespace to prevent au

... View full README on GitHub