dudaster

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.
<h4>Content Management</h4>
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, and handle bulk SEO fields including Yoast SEO meta, titles, and social previews — all in a single conversation. What used to take hours of dashboard work can be delegated to your AI in minutes.
<h4>Safety You Control</h4>
AICOM puts you in charge at every level:
<ul>
<li>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.</li>
<li>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.</li>
<li>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.</li>
<li>Dry-run mode — test any operation before it runs. See exactly what would change without touching live data.</li>
<li>Confirm flag — destructive operations require an explicit <code>"confirm": true</code> parameter. Accidental deletions are prevented by design.</li>
</ul>
<h4>Backup & Restore</h4>
Before every significant change, your agent can snapshot the current state of a post or term. If something goes wrong, restore the exact previous version in one call. Backups are stored in the database, organised by session, and can be cleaned up automatically based on age or total size.
<h4>Full Audit Trail</h4>
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.
<h4>Accessibility Audits — New in v3.2.0</h4>
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:
<ul>
<li>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.</li>
<li>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.</li>
<li>Fix in place — set alt text on any media library image in one call. Pass an empty string to correctly mark it as decorative (<code>aria-hidden</code>). Full dry-run support so you can preview changes before saving.</li>
<li>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.</li>
</ul>
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.
<h4>Supported Modules</h4>
<ul>
<li>WordPress Core — posts, pages, custom post types, terms, meta, options, menus, plugins</li>
<li>Media — upload, update, delete media; direct file system access</li>
<li>Users & Roles — create, update, manage users and role assignments</li>
<li>Backup — per-post and per-term snapshots, session-based restore</li>
<li>Sessions — named audit sessions with grouped action history</li>
<li>Accessibility — site-wide alt text audit, post-level WCAG check, alt text fixes</li>
<li>WooCommerce (optional) — products, categories, settings</li>
<li>Elementor (optional) — page creation from template, widget inspection, theme builder conditions</li>
<li>Polylang (optional) — translations, language assignment, string management</li>
<li>Yoast SEO (optional) — read and write SEO titles, meta descriptions, Open Graph and Twitter card fields; bulk audit across all posts in one session</li>
<li>Clautron (optional) — blueprint management, capability catalog, event analytics</li>
<li>ECS (optional) — Ele Custom Skin color schemes, font schemes, custom looks</li>
</ul>
<h4>Who is this for?</h4>
<ul>
<li>Content teams using Claude, ChatGPT, or any AI assistant who want it to publish and update WordPress content directly</li>
<li>Agencies managing multiple client sites and wanting AI-assisted workflows with a full paper trail</li>
<li>Developers building AI-powered WordPress tools or automation pipelines</li>
<li>Accessibility specialists who want to audit and remediate WCAG issues at scale with AI assistance</li>
<li>Claude Code users — point AICOM as an MCP server from your terminal and control WordPress alongside your code</li>
<li>OpenAI Codex users — connect Codex to your site via AICOM’s MCP endpoint and let it manage content as part of your dev workflow</li>
<li>ChatGPT, Copilot Studio, Dify, n8n users — import the OpenAPI schema URL into any OpenAPI-compatible client; all tools are discovered automatically with Bearer auth</li>
<li>OpenClaw / Celine / Goose users — native MCP connector, works out of the box</li>
</ul>
<h4>How it works</h4>
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.
<pre><code>AI Agent → AICOM Endpoint → WordPress
</code></pre>
<h4>API Key Scopes</h4>
Each API key is granted specific scopes — you control exactly what each AI agent can and cannot do:
<pre><code>read.wp, `write.wp.posts`, `manage.taxonomies`, `manage.meta`, `manage.wordpress.settings`, `manage.media`, `manage.files`, `manage.users`, `manage.plugins`, `manage.backups`, `manage.a11y`, `manage.woocommerce.products`, `manage.woocommerce.settings`, `manage.elementor`, `manage.polylang`, `manage.yoast`, `manage.clautron`
</code></pre>
<h4>Endpoint</h4>
REST API: 
 POST /wp-json/aicom/v1/mcp
Fallback (no mod_rewrite required): 
 POST /?aicom=1
Health check: 
 GET /?aicom=1
<h4>Authentication</h4>
<pre><code>Authorization: Bearer aicom_XXXXXXXX_<secret>
</code></pre>
or:
<pre><code>X-API-Key: aicom_XXXXXXXX_<secret>
</code></pre>
<h4>MCP Request Example</h4>
<pre><code>{"jsonrpc":"2.0","method":"tools/call","params":{"name":"wp.posts.list","arguments":{"post_type":"post","posts_per_page":10}},"id":1}
</code></pre>

AICOM – AI Commander

Use your AI subscription to manage WordPress: create Elementor pages, update content, automate tasks, and stay fully in control.

skswave

When an AI agent visits your WordPress site today, it has to scrape HTML, guess your organization, and parse legal pages written for humans. Rootz AI Discovery fixes this by serving structured, machine-readable data that AI agents can understand instantly.
What it does:
<ul>
<li>Serves <code>/.well-known/ai</code> with your organization identity, capabilities, and policies (RFC 8615)</li>
<li>Structured content endpoint at <code>/.well-known/ai/content</code> with pages, posts, media, custom types</li>
<li>Auto-generates knowledge base at <code>/.well-known/ai/knowledge</code></li>
<li>AI-optimized content feed at <code>/.well-known/ai/feed</code></li>
<li>Machine-readable policies at <code>/.well-known/ai/policies</code></li>
<li>Adds <code><link rel="ai-discovery"></code> tag and HTTP Link header to every page</li>
<li>Generates <code>/llms.txt</code> from your site structure</li>
<li>Provides REST API endpoints for AI agents (<code>/wp-json/rootz/v1/</code>)</li>
<li>Registers WebMCP tools for browser-based AI assistants</li>
<li>Machine-readable content licensing (CC-BY, CC0, All Rights Reserved, etc.)</li>
<li>AI training opt-in/opt-out declaration</li>
<li>Cryptographic signing — every ai.json response and llms.txt is digitally signed (ECDSA secp256k1), proving origin and content integrity</li>
<li>Digital identity via plugin wallet (Ethereum-compatible address generated locally)</li>
<li>Content assertion types (factual, editorial, creative-work) per item</li>
<li>AI access metrics and analytics dashboard</li>
<li>Self-scoring status endpoint for monitoring</li>
</ul>
Signed for origin and quality. Each plugin install generates a unique cryptographic identity. Every manifest is digitally signed so AI agents can verify the data came from your site and hasn’t been tampered with. No other WordPress plugin does this. For more information on managing your digital identity, see <a href="https://rootz.global/identity" rel="nofollow ugc">rootz.global/identity</a>.
Core data is generated locally from your existing WordPress content. Optional AI-powered features use external services (see Third-Party Services below).
Open standard. The AI Discovery Standard is CC-BY-4.0 licensed. See <a href="https://rootz.global/ai-discovery" rel="nofollow ugc">rootz.global/ai-discovery</a>.
<h4>Third-Party Services</h4>
This plugin connects to external services in the following cases. All connections use HTTPS.
1. Rootz AI Proxy (optional) 
When you use the “Auto-Populate with AI” feature to generate your site description, summary, or core concepts, the plugin sends your site URL and basic metadata to: 
* Service: <code>dev.epistery.host/agent/rootz/ai-proxy/</code> 
* Data sent: Site URL, title, tagline 
* When: Only when you click “Auto-Populate” in the admin panel 
* Privacy: <a href="https://rootz.global/privacy" rel="nofollow ugc">rootz.global/privacy</a>
2. Anthropic API (optional) 
If you enter your own Anthropic API key in settings, the plugin can call the Anthropic API directly as a fallback for AI content generation: 
* Service: <code>api.anthropic.com</code> 
* Data sent: Site URL, title, tagline (same as above) 
* When: Only when you click “Auto-Populate” and have entered an API key 
* Privacy: See https://www.anthropic.com/legal/privacy
3. Plugin Updates (automatic) 
The plugin checks for available updates from the Rootz update server: 
* Service: <code>rootz.global/api/plugin/update.json</code> 
* Data sent: None (read-only GET request) 
* When: Automatically every 12 hours (uses WordPress transients) 
* Note: Disabled when the plugin is installed from WordPress.org (WP.org provides updates instead) 
* Privacy: <a href="https://rootz.global/privacy" rel="nofollow ugc">rootz.global/privacy</a>
4. License Verification (automatic when configured) 
If you enter an Owner Identity in the Account tab, the plugin verifies your subscription status: 
* Service: <code>rootz.global/api/license/status</code> 
* Data sent: Your Owner Identity address (a public blockchain address, not personal data) 
* When: On admin page load, cached for 12 hours 
* Privacy: <a href="https://rootz.global/privacy" rel="nofollow ugc">rootz.global/privacy</a>
<h3>Privacy</h3>
<h4>Data Storage</h4>
All structured data (organization identity, policies, content) is generated from your existing WordPress content and stored in wp_options. No user data is collected.
<h4>External Services</h4>
The plugin connects to external services only when specific features are used. See the “Third-Party Services” section in the Description tab for complete details including what data is sent, when, and links to each service’s privacy policy.
<h4>Cookies</h4>
This plugin does not set any cookies.
<h4>Analytics</h4>
The plugin tracks AI agent visits to your /.well-known/ai endpoints in a local database table (wp_rootz_metrics). This data stays on your server and is never transmitted externally. You can view it in the Analytics tab.

Rootz AI Discovery

Make your WordPress site AI-agent-ready. Structured identity, policies, content API, and WebMCP tools at /.well-known/ai.

AICOM – AI Commander vs Rootz AI Discovery