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.

Respira for WordPress

<p>Inhale: MCP Abilities is a small, focused utility that solves one problem: the default WordPress MCP server (provided by the official MCP Adapter plugin) does not expose any registered abilities by default. Site administrators have to write PHP filters to opt each ability into the public MCP surface.</p>
<p>This is the workaround pattern documented in WordPress contributor blog posts and developer guides since the MCP Adapter shipped. Inhale: MCP Abilities replaces the PHP-filter workaround with a simple settings page.</p>
<p>Once installed and activated, you’ll find a new page at Settings > Inhale: MCP Abilities where you can check off the abilities you want exposed to your default MCP server.</p>
<h4>What the Inhale: MCP Abilities plugin does</h4>
<ul>
<li>Lists every registered WordPress ability across all active plugins and themes</li>
<li>Lets you select which abilities are exposed to the default MCP server with simple checkboxes</li>
<li>Shows annotation metadata (read-only, destructive, idempotent) on each ability so you can make informed decisions</li>
<li>Requires explicit confirmation when you inhale an ability marked as destructive</li>
<li>Provides connection info for popular MCP clients (Claude Desktop, Cursor, Claude Code)</li>
<li>Respects each ability’s own permission_callback. The Inhale: MCP Abilities plugin controls visibility, not authorization.</li>
</ul>
<h4>What the Inhale: MCP Abilities plugin doesn’t do</h4>
<ul>
<li>Inhale: MCP Abilities does not run any MCP servers, transports, or authentication. Those are handled by the official MCP Adapter plugin, which the Inhale: MCP Abilities plugin extends.</li>
<li>Inhale: MCP Abilities does not register any abilities of its own. It only toggles visibility of abilities other plugins have registered.</li>
<li>Inhale: MCP Abilities does not phone home, collect telemetry, or make external network requests.</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress 6.8 or later (Abilities API in core since 6.9; 6.8 requires the Abilities API plugin)</li>
<li>PHP 7.4 or later</li>
<li>The official WordPress MCP Adapter plugin installed and active</li>
</ul>
<h4>About MCP</h4>
<p>Model Context Protocol (MCP) is an open specification originally developed by Anthropic. Inhale: MCP Abilities is a third-party plugin and is not affiliated with, endorsed by, or sponsored by Anthropic. Respira is an independent company.</p>
<h4>About Respira</h4>
<p>The Inhale: MCP Abilities plugin is built and maintained by Respira, which ships AI infrastructure for WordPress. The main product is Respira for WordPress, a safety layer that registers 130+ abilities across 12 page builders (Elementor, Bricks, Divi, Beaver Builder, Oxygen, Breakdance and 6 more) with snapshot-before-write protection, render validation and one-click rollback. Inhale: MCP Abilities is a free utility offered to the WordPress community. Learn more at https://respira.press/inhale?utm_source=inhale&utm_medium=wp-org&utm_campaign=readme-description.</p>


Inhale: MCP Abilities by Respira

A small settings page that lets WordPress site administrators choose which registered abilities are exposed to the default MCP server.

Abilities Bridge vs Inhale: MCP Abilities by Respira