hamidxazad

Botailor ModelContext Integrator for AI is a powerful WordPress plugin that exposes selected posts and pages as AI-readable endpoints via the Model Context Protocol (MCP). This plugin provides a clean, secure way to make your WordPress content available to AI systems, external applications, and other services that need structured access to your content.
The plugin features granular permission control, allowing you to set specific permissions (Read, Write, Update, Delete) for each piece of content, ensuring your data remains secure while providing flexible access for authorized applications.
<h4>Features</h4>
<ul>
<li>Selective Content Exposure: Choose which posts and pages to expose via the API</li>
<li>Granular Permission Control: Set individual permissions (Read, Write, Update, Delete) for each content item</li>
<li>Full CRUD Operations: Create, Read, Update, and Delete posts and pages via API</li>
<li>REST API Endpoints: Clean, standardized endpoints under <code>/wp-json/mcia/v1/</code></li>
<li>Master Endpoint: List all available endpoints with <code>/wp-json/mcia/v1/endpoints</code></li>
<li>Manifest Endpoint: Auto-generated manifest at <code>/wp-json/mcia/v1/manifest</code> and <code>/.well-known/mcp-manifest.json</code></li>
<li>Admin Interface: Easy-to-use settings page with search, pagination, and bulk actions</li>
<li>Security: Built-in authentication, nonces, and capability checks</li>
<li>WooCommerce Filtering: Automatically excludes WooCommerce products and pages</li>
<li>Real-time Updates: Changes take effect immediately</li>
</ul>
<h4>API Endpoints</h4>
Read Operations: 
* <code>GET /wp-json/mcia/v1/manifest</code> – Get manifest (all exposed content) 
* <code>GET /wp-json/mcia/v1/endpoints</code> – List all available endpoints 
* <code>GET /wp-json/mcia/v1/{slug}</code> – Get individual content by slug
CRUD Operations (Require Authentication): 
* <code>POST /wp-json/mcia/v1/posts</code> – Create new post 
* <code>PUT /wp-json/mcia/v1/posts/{id}</code> – Update existing post 
* <code>DELETE /wp-json/mcia/v1/posts/{id}</code> – Delete post 
* <code>POST /wp-json/mcia/v1/pages</code> – Create new page 
* <code>PUT /wp-json/mcia/v1/pages/{id}</code> – Update existing page 
* <code>DELETE /wp-json/mcia/v1/pages/{id}</code> – Delete page
Well-known Endpoint: 
* <code>GET /.well-known/mcp-manifest.json</code> – Public manifest (no authentication required)
<h4>Response Format</h4>
Each content endpoint returns:
<pre><code>`json
</code></pre>
{ 
 “title”: “Page/Post title”, 
 “content”: “Page/Post content”, 
 “content_html”: “HTML formatted content”, 
 “description”: “Short description”, 
 “slug”: “content-slug”, 
 “type”: “post|page”, 
 “status”: “publish”, 
 “date”: “2024-01-01 00:00:00”, 
 “modified”: “2024-01-01 00:00:00”, 
 “author”: “Author Name”, 
 “featured_image”: “image-url”, 
 “meta”: {}, 
 “url”: “permalink” 
} 
 `
<h3>Testing the Plugin</h3>
<h3>Quick Test Setup</h3>
<ol>
<li>
Configure Authentication:
<ul>
<li>Go to Settings > Botailor ModelContext Integrator for AI</li>
<li>Set a username and password for API access</li>
<li>Save the credentials</li>
</ul>
</li>
<li>
Enable Content:
<ul>
<li>Select which posts/pages to expose</li>
<li>Set permissions (Read, Write, Update, Delete) for each item</li>
<li>Use bulk actions to enable multiple items at once</li>
</ul>
</li>
<li>
Test Read Operations: 
 `bash
Test manifest (no auth required)
curl “http://yoursite.com/.well-known/mcp-manifest.json”
Test authenticated manifest
curl -u “username:password” “http://yoursite.com/wp-json/mcia/v1/manifest”
Test individual content
curl -u “username:password” “http://yoursite.com/wp-json/mcia/v1/your-post-slug” 
 `
</li>
<li>
Test CRUD Operations: 
 `bash
Create a new post
curl -u “username:password” -X POST “http://yoursite.com/wp-json/mcia/v1/posts” \ 
 -H “Content-Type: application/json” \ 
 -d ‘{“title”: “Test Post”, “content”: “Test content”, “status”: “publish”}’
Update a post (replace {id} with actual post ID)
curl -u “username:password” -X PUT “http://yoursite.com/wp-json/mcia/v1/posts/{id}” \ 
 -H “Content-Type: application/json” \ 
 -d ‘{“title”: “Updated Title”, “content”: “Updated content”}’
Delete a post (replace {id} with actual post ID)
curl -u “username:password” -X DELETE “http://yoursite.com/wp-json/mcia/v1/posts/{id}” 
 `
</li>
<li>
Test Permission System:
<ul>
<li>Try to update/delete content that only has “Read” permission</li>
<li>Verify that operations are blocked with proper error messages</li>
<li>Test that content with appropriate permissions works correctly</li>
</ul>
</li>
</ol>
<h3>Expected Results</h3>
<ul>
<li>Manifest: Should list all exposed content with metadata</li>
<li>Individual Content: Should return full post/page data with permissions</li>
<li>CRUD Operations: Should respect permission settings and authentication</li>
<li>Error Handling: Should return clear error messages for unauthorized operations</li>
</ul>
<h3>Development</h3>
This plugin follows WordPress coding standards and best practices:
<ul>
<li>Proper sanitization and validation</li>
<li>Nonce verification for security</li>
<li>Capability checks for admin functions</li>
<li>Modular code structure with 4-letter prefix naming convention</li>
<li>Comprehensive error handling</li>
<li>Responsive admin interface</li>
<li>Granular permission system</li>
<li>Full CRUD operations with authentication</li>
</ul>
<h3>Support</h3>
Author: Hamid Azad 
GitHub: <a href="https://github.com/hamidhosenazad" rel="nofollow ugc">https://github.com/hamidhosenazad</a> 
Email: hamidxazad@gmail.com
For support, feature requests, or bug reports, please visit the plugin’s GitHub repository or contact the author directly.

Botailor ModelContext Integrator for AI

Expose selected posts & pages as AI-readable endpoints via the Model Context Protocol (MCP) with granular permission control and full CRUD operations.

Respira for WordPress

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.
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.
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.
<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>
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.
<h4>About Respira</h4>
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.

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.

Botailor ModelContext Integrator for AI vs Inhale: MCP Abilities by Respira