El Proximus

<p><strong>Making Connections Possible</strong> | Now with Claude Opus 4.8, in-chat image attachments and screenshots, GPT-5.5, and Custom Apps in ChatGPT</p>
<p>Abilities Bridge connects AI to your WordPress site. Use the built-in admin chat, connect via MCP to Claude Desktop, or integrate with other MCP-compatible applications. Supports both Anthropic (Claude) and OpenAI models.</p>
<h4>Key Features</h4>
<ul>
<li>Admin chat interface for direct AI interaction</li>
<li>Image attachments in chat — upload images or capture a browser-approved screenshot (can be disabled in settings)</li>
<li>MCP server for Claude Desktop, ChatGPT, and other MCP clients</li>
<li>Persistent memory storage across conversations</li>
<li>Abilities execution with 7-gate permission controls</li>
<li>Integrated Connected Plugins — discover and approve AI abilities that other plugins register, with per-ability permission controls</li>
<li>Claude and OpenAI model support</li>
<li>OAuth 2.0 authentication for MCP connections</li>
</ul>
<h4>Four Ways to Connect</h4>
<ol>
<li><strong>Admin Chat</strong> – Built-in interface using your Anthropic or OpenAI API key</li>
<li><strong>Claude Custom Connector</strong> – Connect Claude Desktop using your Claude subscription (no API key needed)</li>
<li><strong>ChatGPT Developer Mode</strong> – Connect ChatGPT using the built-in MCP endpoint with OAuth</li>
<li><strong>Local MCP Config</strong> – Connect Claude Code and other apps using API key or Claude account</li>
</ol>
<h4>Requirements</h4>
<ul>
<li>WordPress 6.2+, PHP 7.4+</li>
<li>Anthropic API key, OpenAI API key, or Claude account (depending on connection method)</li>
<li>HTTPS required for MCP OAuth 2.0 connections</li>
</ul>
<h3>External Services</h3>
<p><strong>This plugin connects to external API services.</strong></p>
<p>This plugin communicates with Anthropic’s Claude API (https://api.anthropic.com) and/or OpenAI’s API (https://api.openai.com) to provide AI functionality. Data is only sent when you actively use the chat interface or MCP tools. No background data collection or telemetry occurs.</p>
<h4>Data Sent</h4>
<ul>
<li>Chat messages and prompts</li>
<li>Memory contents</li>
<li>Abilities execution requests and results</li>
</ul>
<h4>Legal & Privacy</h4>
<ul>
<li>Anthropic Privacy Policy: https://www.anthropic.com/legal/privacy</li>
<li>Anthropic Terms: https://www.anthropic.com/legal/consumer-terms</li>
<li>OpenAI Privacy Policy: https://openai.com/policies/privacy-policy</li>
<li>OpenAI Terms: https://openai.com/policies/terms-of-use</li>
<li>Abilities Bridge Privacy Policy: https://aisystemadmin.com/privacy-policy</li>
<li>Abilities Bridge Terms: https://aisystemadmin.com/terms-and-conditions/</li>
</ul>
<p>By using this plugin, you acknowledge that data will be transmitted to your selected AI provider for processing.</p>
<h3>Privacy & Security</h3>
<h4>Data Transmission</h4>
<p>This plugin sends data to Anthropic’s API (https://api.anthropic.com) or OpenAI’s API (https://api.openai.com) when you interact with the AI. This includes chat messages, memory contents, and abilities execution requests. You control what data is sent – the AI only accesses data when you use it.</p>
<h4>Security</h4>
<ul>
<li>Permission controls with explicit consent for all write capabilities</li>
<li>7-gate ability authorization system</li>
<li>Isolated memory storage with size limits (50MB total)</li>
<li>Full activity logging and audit trails</li>
<li>OAuth tokens encrypted with AES-256-CBC</li>
<li>MCP access requires authentication for every method, including discovery (initialize, tools/list, ping); unauthenticated requests receive an HTTP 401 OAuth challenge</li>
<li>All admin actions protected with nonce verification and capability checks</li>
</ul>
<h4>Data Retention</h4>
<p>Conversations and logs are stored in your WordPress database until manually deleted. Refer to your provider’s privacy policy for their data retention practices.</p>
<h4>No Telemetry</h4>
<p>This plugin does NOT send usage statistics, telemetry, or analytics to the plugin developer.</p>
<h3>Support</h3>
<p>For support, visit https://aisystemadmin.com</p>
<h3>License</h3>
<p>This plugin is licensed under the GPL v2 or later.</p>


Abilities Bridge


This plugin allows you to easily connect to abilities on your WordPress site and use them as function calls. The built-in admin chat is very useful. Thanks!


Easy to Connect Abilities!

MCP server for WordPress. Connect Claude AI or OpenAI to execute WordPress Abilities with configurable permissions.

Jordy Meow

<p><strong>Chagency</strong> is the first chatbot to ship directly on top of the new AI Client introduced in WordPress 7.0 — <code>wp_ai_client_prompt()</code>, Connectors, and the Abilities API. Every prompt flows through WordPress core, every provider is a Connector you already configured under <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Connectors</strong>, and every action it exposes is a registered Ability that other plugins (and other AI agents) can call.</p>
<p>There is no other plugin on wordpress.org that builds on <code>wp_ai_client_prompt()</code> today. Chagency is the reference case: a small, native chatbot that proves the framework works, ships zero vendor SDKs, and grows alongside the Abilities API into a real agent.</p>
<p>It runs in the WordPress admin and, when you turn it on, on every page of your public site. The name (chat + ai + ency) is meant as a small bridge between the new AI primitives shipped with WordPress and the broader world of chat and agents. It starts as a chatbot today and turns into an agent tomorrow, without a rename.</p>
<h3>🪨 Built on WordPress, period</h3>
<p>Chagency relies entirely on what WordPress 7 ships in core:</p>
<ul>
<li><code>wp_ai_client_prompt()</code>, the AI Client API.</li>
<li><code>wp_get_connectors()</code>, the Connectors API.</li>
<li><code>wp_register_ability()</code> / <code>wp_get_ability()</code>, the Abilities API.</li>
<li><code>@wordpress/components</code>, <code>@wordpress/element</code>, <code>@wordpress/boot</code>, the Gutenberg toolkit.</li>
</ul>
<p>That is the entire dependency surface. <strong>No bundled AI vendor SDKs, no third-party JavaScript libraries beyond the Gutenberg stack, no telemetry, no phone-home.</strong> The plugin stays small on purpose: fewer moving parts means less friction, fewer security holes, less to break when WordPress, browsers, or providers change.</p>
<p>You will need at least one AI provider plugin (e.g. <em>AI Provider for Anthropic</em>, <em>AI Provider for Google</em>, <em>AI Provider for OpenAI</em>) to talk to a model. That is WordPress 7’s architecture: providers are separate plugins that register a Connector. They are not a Chagency dependency.</p>
<p>💡 <strong>Tip:</strong> For the smoothest setup, install <a href="https://wordpress.org/plugins/ai-engine/" rel="ugc">AI Engine</a>. It registers every AI provider it manages as a Connector, so a single configuration covers all your WordPress 7 AI plugins (including Chagency). Every request then flows through one clean, unified system.</p>
<h3>🪄 What you get</h3>
<ul>
<li>A floating chat panel pinned to the bottom-right of every page (admin and / or public site, controlled by two independent toggles).</li>
<li>A single settings page under <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Chagency</strong>, with the bare minimum: where to show the chatbot, the chat title, the greeting, the system instruction, and the model preference.</li>
<li>Live updates: flipping a toggle in Settings shows or hides the launcher immediately on the same page, no reload needed.</li>
<li>Per-provider <strong>Test</strong> buttons that fire a canary prompt and report round-trip time.</li>
<li>Conversation persistence in your browser’s localStorage, scoped per user.</li>
<li>Placeholder expansion (<code>{user_name}</code>, <code>{site_name}</code>, <code>{current_page}</code>, <code>{current_url}</code>, <code>{user_role}</code>, <code>{site_url}</code>) so the assistant always knows who and where it is.</li>
<li>Exposed as an Ability (<code>chagency/send-message</code>) so other plugins, MCP clients, and AI agents can invoke Chagency directly.</li>
</ul>
<h3>🚀 Getting started</h3>
<ol>
<li>Install and activate <strong>Chagency</strong>.</li>
<li>Install and configure at least one AI provider plugin under <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Connectors</strong> (we recommend <a href="https://wordpress.org/plugins/ai-engine/" rel="ugc">AI Engine</a>, which exposes all its providers as Connectors at once).</li>
<li>Click the chat launcher in the bottom-right of any admin page and start talking.</li>
<li>Want it on the public site too? Open <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Chagency</strong> and flip the second toggle.</li>
</ol>
<h3>🙋 Frequently Asked Questions</h3>
<h4>Why “Chagency”?</h4>
<p>It’s a portmanteau of <em>chat</em>, <em>AI</em>, and a bit of <em>agent</em>. Not “agency” in the sense of a marketing shop. The plugin starts as a minimal chatbot for the new WordPress 7 AI framework and grows alongside the Abilities API into a true agent.</p>
<h4>Does it need WordPress 7?</h4>
<p>Yes. It uses <code>wp_ai_client_prompt()</code>, <code>wp_get_connectors()</code>, and the Abilities API, all added in WordPress 7.0. On older versions it refuses to boot and tells you why.</p>
<h4>Which AI providers are supported?</h4>
<p>Whatever you configure under <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Connectors</strong>. Chagency is provider-agnostic. Anthropic, Google, OpenAI, or any third-party Connector are treated equally.</p>
<h4>Can visitors on the front end use it?</h4>
<p>Yes. Open <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Chagency</strong> and turn on <em>Show on the public site</em>. The chat then appears for every visitor, signed in or not.</p>
<h4>Does it store my conversations?</h4>
<p>No. Conversations live only in your own browser (localStorage, per user). Hit <em>Reset</em> in the panel to clear them. Nothing is stored server-side.</p>
<h4>Can I use it as a building block in my own plugin?</h4>
<p>Yes. The <code>chagency/send-message</code> Ability is registered on <code>wp_abilities_api_init</code> and can be called with <code>wp_get_ability( 'chagency/send-message' )->execute( array( 'message' => '...' ) )</code>.</p>
<h3>Source code</h3>
<p>The unminified React / JavaScript source is shipped inside the plugin folder under <code>src/</code>, alongside the compiled output in <code>build/</code>. Public source repository: https://github.com/jordymeow/chagency</p>
<p>To rebuild from source:</p>
<pre><code>pnpm install && pnpm run build
</code></pre>
<p>The build is <code>@wordpress/scripts</code> (webpack) with no custom plugins or transforms.</p>


Chagency


Nobody cares. Or maybe some do. I do! 😼 The first and only chatbot (as of today) to use the AI Client that ships with WordPress (from v7). This chatbot is perfect for testing the AI Client and the AI providers built for it.


The 1st and only chatbot to use the AI Client

The first chatbot built natively on the WordPress 7 AI Client. No bundled SDKs, no third-party JavaScript, no telemetry.

Abilities Bridge vs Chagency