AICOM – AI Commander
AICOM – AI Commander connects your WordPress site to any AI agent via MCP (Model Context Protocol) or OpenAPI. Use your existing AI subscription — Claude Code, OpenAI Codex, ChatGPT Custom GPTs, Copilot Studio, Dify, n8n, OpenClaw, Celine, Goose, or any MCP-compatible client — to manage content, build pages, run audits, and automate repetitive tasks, all without leaving your AI interface. No more copy-pasting between your AI assistant and the WordPress dashboard. Describe what you want, and your agent does it — safely, with a full record of every action. Content Management Create, update, and publish posts, pages, and custom post types directly from your AI agent. Build and duplicate Elementor pages, manage menus, upload media, update taxonomies, translate content with Polylang or WPML, and handle bulk SEO fields — titles, meta descriptions, robots directives, social previews — with Yoast SEO or SEOPress, whichever is active on your site. All in a single conversation. What used to take hours of dashboard work can be delegated to your AI in minutes. Safety You Control AICOM puts you in charge at every level: Scope-based API keys — each key grants access only to the operations you explicitly allow. One key for read-only content review, another for full publishing access. Soft Lock / Hard Lock — freeze all write operations (Soft) or block everything except public tools (Hard) with one click from the admin bar or Safety page. Working Hours Schedule — automatically apply Soft or Hard Lock outside your configured working hours and days. Agents can’t make changes at night or on weekends unless you explicitly override it. Dry-run mode — test any operation before it runs. See exactly what would change without touching live data. Confirm flag — destructive operations require an explicit "confirm": true parameter. Accidental deletions are prevented by design. Backup & Restore AICOM automatically snapshots a post, term, or Elementor page/template right before your agent updates, trashes, deletes, or edits it — no extra step required, even if the agent never calls a backup tool itself. If something goes wrong, restore the exact previous version in one call, or undo an entire session at once: the Snapshots page lists every session that touched content, with a one-click Restore session button that reverts every post, term, and Elementor page it modified — including Elementor Theme Builder display conditions. Backups are stored in the database and can be cleaned up automatically based on age or total size. Full Audit Trail Every request is logged: timestamp, remote IP, API key label, tool used, parameters, result, and response time. Logs are grouped into named sessions — when an agent opens a session, all its actions are recorded together so you can review, replay, or undo an entire workflow at once. The Audit Logs page includes a session activity chart and a direct Restore button for each session. Built for Reliable Automation AICOM speaks strict MCP JSON-RPC: every successful call returns a content field for full client compatibility, protocol errors use standard integer codes, and errors from a tool that actually ran are reported as isError so your agent can see and react to them. Pass an idempotency_key on any write call and a retried request (dropped connection, flaky client) returns the original result instead of repeating the action — no duplicate posts from an accidental double-send. Responses are hardened against corrupted output, so your agent always gets valid JSON back. Works Well With Small & Local Models Not every AI agent is Claude or GPT-4 class. AICOM is built to stay usable even for smaller, local, or context-constrained models: tools/search — keyword search over tool names and descriptions, tuned for models that don’t know exact tool names: handles full-sentence queries (“how do I add a photo to my page”), common synonyms (shop → WooCommerce, translate → Polylang/WPML), typo tolerance, and plurals. tools/describe — fetch one tool’s full parameter schema by exact name, on demand — pairs with tools/search so a model never has to load the entire tool catalog just to find what it needs. Compact Tool List (per API key) — an optional setting that strips parameter descriptions from tools/list to cut context size by roughly a third, while always keeping every parameter’s name, type, and whether it’s required — a model can still build a correct call without the extra explanatory text. Off by default; capable models see the full list as before. Scoped discovery — tools/list only ever shows the tools a key can actually call. A key without WooCommerce access never sees WooCommerce tools, so a smaller model isn’t wading through options it’s not allowed to use anyway. Reusable Skills Let your agent turn a workflow it just performed into a saved, reusable recipe. After finishing a session, AICOM can suggest saving what was done — the exact sequence of tool calls, rules, and expected inputs — as a named Skill. Next time a similar task comes up, the agent fetches the Skill and follows it, instead of re-figuring out the same multi-step process from scratch. Skills are versioned (every edit keeps a full revision history), matched by similarity before creating a duplicate, and scoped like any other capability — a key needs manage.skills to create or edit one. Accessibility Audits — New in v3.2.0 AICOM now includes a dedicated Accessibility module so your AI agent can audit and fix WCAG issues across your entire site — no external tools or services required: Site report — instantly see how many images are missing alt text across your entire media library, with a ranked preview of the top offenders and a percentage score. Post audit — scan any post or page for heading hierarchy errors (missing H1, skipped heading levels), images without alt text, and links with non-descriptive anchor text (“click here”, “read more”). Each issue is rated by severity and the post receives an overall accessibility score from 0 to 100. Fix in place — set alt text on any media library image in one call. Pass an empty string to correctly mark it as decorative (aria-hidden). Full dry-run support so you can preview changes before saving. Screenshot before & after — combine AICOM’s audit tools with your AI agent’s browser capabilities to capture a visual record of the page before and after remediation. A typical AI-driven accessibility workflow: run the site report, get the list of problem images, let the agent analyse each image visually and write descriptive alt text, apply the fixes — then run the audit again to confirm the score improved. All in one session, with a full audit trail. Supported Modules WordPress Core — posts, pages, custom post types, terms, meta, options, menus, plugins Media — upload, update, delete media; direct file system access Users & Roles — create, update, manage users and role assignments Backup — automatic snapshots for posts, terms, and Elementor pages/templates before every write; session-wide restore Sessions — named audit sessions with grouped action history Accessibility — site-wide alt text audit, post-level WCAG check, alt text fixes WooCommerce (optional) — products, categories, settings Elementor (optional) — page creation from template, widget inspection, theme builder conditions Polylang (optional) — translations, language assignment, string management, and one-call bilingual post pair creation WPML (optional) — translation language assignment and translation-group linking for posts and taxonomy terms Yoast SEO (optional) — read and write SEO titles, meta descriptions, Open Graph and Twitter card fields; bulk audit across all posts in one session SEOPress (optional) — read and write SEO titles, meta descriptions, robots directives, canonical URLs, Open Graph and Twitter card fields; bulk audit across all posts in one session Skills (optional) — save, version, and run reusable multi-step workflows Clautron (optional) — blueprint management, capability catalog, event analytics ECS (optional) — Ele Custom Skin color schemes, font schemes, custom looks Who is this for? Content teams using Claude, ChatGPT, or any AI assistant who want it to publish and update WordPress content directly Agencies managing multiple client sites and wanting AI-assisted workflows with a full paper trail Developers building AI-powered WordPress tools or automation pipelines Accessibility specialists who want to audit and remediate WCAG issues at scale with AI assistance Claude Code users — point AICOM as an MCP server from your terminal and control WordPress alongside your code OpenAI Codex users — connect Codex to your site via AICOM’s MCP endpoint and let it manage content as part of your dev workflow ChatGPT, Copilot Studio, Dify, n8n users — import the OpenAPI schema URL into any OpenAPI-compatible client; all tools are discovered automatically with Bearer auth OpenClaw / Celine / Goose users — native MCP connector, works out of the box How it works AICOM exposes a secure HTTP endpoint on your WordPress site. Your AI agent sends structured MCP requests, AICOM authenticates the request, checks scopes and lock state, executes the operation, logs it, and returns a structured response. AI Agent → AICOM Endpoint → WordPress API Key Scopes Each API key is granted specific scopes — you control exactly what each AI agent can and cannot do. Dozens of granular scopes are available, grouped by area: read.wp, `write.wp.posts`, `delete.wp.posts`, `manage.taxonomies`, `manage.meta`, `manage.media`, `manage.files`, `manage.wordpress.settings`, `manage.plugins`, `manage.backups`, `manage.a11y`, `manage.users`, `manage.roles`, `manage.skills`, plus one `read.*`/`manage.*` pair per optional integration (WooCommerce, Elementor, Polylang, WPML, Yoast, SEOPress, Clautron). Built-in presets (Content Assistant, Translator, SEO Editor, Site Maintenance, Full Admin, and more) bundle the right scopes for a common role in one click — see the full list and descriptions on the **API Keys** page. Endpoint REST API: POST /wp-json/aicom/v1/mcp Fallback (no mod_rewrite required): POST /?aicom=1 Health check: GET /?aicom=1 Authentication Authorization: Bearer aicom_XXXXXXXX_ or: X-API-Key: aicom_XXXXXXXX_ MCP Request Example {"jsonrpc":"2.0","method":"tools/call","params":{"name":"wp.posts.list","arguments":{"post_type":"post","posts_per_page":10}},"id":1}
Airano MCP Bridge
Airano MCP Bridge is the official companion plugin for MCP Hub (source) — the AI-native management hub for WordPress, WooCommerce, and self-hosted services. It extends the WordPress REST API with dedicated routes that AI agents (Claude, ChatGPT, Cursor, VS Code Copilot) and the MCP Hub server rely on: SEO meta routes — read and write Rank Math SEO and Yoast SEO metadata for posts, pages, and WooCommerce products. Media upload helper routes — accept raw-binary uploads via php://input, which bypasses the upload_max_filesize PHP limit (still bounded by post_max_size). Unlocks reliable hero-image and large-asset uploads for AI-agent workflows. Capability probe — reports the effective PHP + WordPress upload limits so MCP Hub can pick the right upload path automatically. Features: Rank Math SEO Support — Full access to all Rank Math meta fields Yoast SEO Support — Full access to all Yoast SEO meta fields WooCommerce Compatible — Works with product post types MCP Hub media pipeline — bypasses upload_max_filesize for AI-agent uploads Secure — Requires WordPress Application Password + capability checks on every route Auto-Detection — Automatically detects active SEO plugin and advertises capabilities Zero Configuration — Works out of the box after activation REST API Endpoints: SEO meta (namespace airano-mcp-bridge/v1) GET/POST /wp-json/airano-mcp-bridge/v1/posts/{id}/seo — Post SEO data GET/POST /wp-json/airano-mcp-bridge/v1/pages/{id}/seo — Page SEO data GET/POST /wp-json/airano-mcp-bridge/v1/products/{id}/seo — Product SEO data (WooCommerce) GET /wp-json/airano-mcp-bridge/v1/status — Plugin status + active SEO plugins MCP Bridge helpers (namespace airano-mcp/v1, added in 2.0.0) GET /wp-json/airano-mcp/v1/upload-limits — Effective PHP + WP upload limits POST /wp-json/airano-mcp/v1/upload-chunk — Raw-body media upload (bypasses upload_max_filesize) GET /wp-json/airano-mcp/v1/capabilities — Effective capabilities + feature flags + available routes (added in 2.1.0) POST /wp-json/airano-mcp/v1/bulk-meta — Batch post/product meta writes in a single HTTP round-trip (added in 2.2.0) GET /wp-json/airano-mcp/v1/export — Structured JSON export: posts, pages, products + media + terms + meta, with post_type/status/since/limit/offset paging (added in 2.3.0) POST /wp-json/airano-mcp/v1/cache-purge — Auto-detects active cache plugins (LiteSpeed, WP Rocket, W3TC, Super Cache, Fastest Cache, SG Optimizer) and invokes their purge API; always flushes object cache (added in 2.4.0) POST /wp-json/airano-mcp/v1/transient-flush — Native transient cleanup with scope=expired/all/pattern (glob); optional site-transient handling on multisite (added in 2.5.0) GET /wp-json/airano-mcp/v1/site-health — Unified site-health snapshot: PHP/MySQL/WP versions, extensions, disk free, active plugins + theme, writability checks (added in 2.6.0) GET|POST|DELETE /wp-json/airano-mcp/v1/audit-hook — Configure + query a webhook that forwards WordPress action events to MCP Hub (HMAC-SHA256 signed, non-blocking) (added in 2.7.0) POST /wp-json/airano-mcp/v1/regenerate-thumbnails — Regenerate attachment sub-sizes via wp_generate_attachment_metadata for a list of IDs or in paged batch mode (added in 2.8.0) POST /wp-json/airano-mcp/v1/upload-and-attach — Raw-body upload + metadata + attach-to-post + set-featured in a single REST call (added in 2.9.0). Query params: attach_to_post, set_featured, title, alt_text, caption, description. Permission: upload_files + edit_post on the target post. POST /wp-json/airano-mcp/v1/opcache-reset — Reset PHP OPcache after a theme/plugin deploy (added in 2.11.0). Permission: manage_options. GET /wp-json/airano-mcp/v1/transients — Read-only inventory of transient keys + expirations; values intentionally never returned (added in 2.11.0). Capped at 500 per call. Permission: manage_options. POST /wp-json/airano-mcp/v1/term-update — Mutate a taxonomy term via wp_update_term (added in 2.11.0). Accepts taxonomy (canonical name or REST base), term_id, and any of name/slug/description/parent. Permission: the taxonomy’s own edit_terms capability, enforced at the route gate. POST /wp-json/airano-mcp/v1/cache-purge — As of 2.11.0 accepts an optional scope body parameter (all / page / object, default all). Designed for MCP Hub — the AI-native management hub for WordPress and self-hosted services. Try the live platform · Source on GitHub.
