WordPress
Secure MCP Server for WordPress Turn any WordPress site into a fully working MCP server.
Что умеет
- Discover Abilities: List what this WordPress site can do. ALWAYS call this first to get the exact ability_name before execute_ability. Optionally filter with `query` (keyword) or `category`. Returns e
- Get Ability Info: Get the full input schema and details for a single ability, when discover_abilities isn't enough. Pass the exact ability_name from discover_abilities.
- Execute Ability: Run one ability on the site. Pass the exact `ability_name` from discover_abilities and its `parameters` (shaped by that ability's input schema; use {} if it takes none). Returns {succ
Какие данные видит
Нужен ли аккаунт
Не нужен: сервер работает без входа
Secure MCP Server for WordPress
Turn any WordPress site into a fully working MCP server. Connect Claude, ChatGPT, Cursor, Gemini, Windsurf, or any MCP-compatible client and let AI read, create, and manage your WordPress content through chat — safely, with you in control.
Unlike integrations that hand AI full admin access, every action is scoped to the roles and abilities you allow, authenticated with self-hosted OAuth 2.1 — the AI never sees your WordPress password.
What your AI can do — 300+ tools, and growing
Manage virtually any part of your WordPress site through natural language. The connector exposes your site's real capabilities to AI and adapts to whatever your site runs — any content type, any custom fields, your page builder, your store, your SEO setup.
- Run your content — create, edit, publish, schedule, organize, and clean up posts, pages, media, categories, tags, and revisions.
- Operate your store — manage products, orders, customers, coupons, and sales reporting end to end.
- Edit your designs — update text, images, links, and styling in your page builder without breaking layouts.
- Administer your site — custom post types and fields, SEO metadata, user accounts and roles, comment moderation, and more.
- Works with your stack — automatically detects and supports popular plugins (WooCommerce, Elementor, Kadence, ACF, Yoast, and others) plus any custom content types your site defines — so capabilities expand as your site does.
From everyday edits to full store operations and site administration — if it's part of running your WordPress site, your AI can do it, scoped to exactly the permissions you allow.
Security & governance (built in, no limits)
- OAuth 2.1 self-hosted authorization: no API keys, no shared passwords.
- Role-based AI access: grant specific tools per WordPress role.
- One-click tool controls: turn any ability on or off.
- Full audit log: every AI action recorded with who, what, and when.
- Built natively on the WordPress Abilities API.
Prerequisite
This connector requires the free Secure MCP Server plugin installed and active on your WordPress site. It's what exposes your site's abilities to AI and handles the OAuth security.
👉 Install it here: https://wordpress.org/plugins/miniorange-secure-mcp-server/
Get started
- Install & activate the Secure MCP Server plugin on your WordPress site.
- Create an agent and grant it abilities for the WordPress roles you choose.
- Connect your AI through the miniOrange - paste your site URL and approve access.
Learn more: https://plugins.miniorange.com/mcp-server-ai-policy-enforcement-wordpress
Список инструментов сервера (3)
Технические названия из tools/list. Нужны только разработчикам.
| discover_abilities | List what this WordPress site can do. ALWAYS call this first to get the exact ability_name before execute_ability. Optionally filter with `query` (keyword) or `category`. Returns each ability's name, a one-line description, and key parameters. |
| get_ability_info | Get the full input schema and details for a single ability, when discover_abilities isn't enough. Pass the exact ability_name from discover_abilities. |
| execute_ability | Run one ability on the site. Pass the exact `ability_name` from discover_abilities and its `parameters` (shaped by that ability's input schema; use {} if it takes none). Returns {success, data} or {success:false, error}. |