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.

airano

<blockquote>
⚠️ This plugin has been superseded by <a href="https://wordpress.org/plugins/airano-mcp-bridge/" rel="ugc">Airano MCP Bridge</a> (slug <code>airano-mcp-bridge</code>). The replacement carries the same SEO routes plus media uploads (bypass <code>upload_max_filesize</code>), bulk meta writes, cache purge, transient flush, site health, audit hook, and thumbnail regeneration. Existing installs of Airano MCP SEO Meta Bridge keep working — no breaking changes — but new installs should use Airano MCP Bridge. An admin notice in v1.3.1+ links to the replacement.
</blockquote>
Airano MCP SEO Bridge is a WordPress plugin that exposes Rank Math SEO and Yoast SEO meta fields via dedicated REST API endpoints. This enables MCP servers, AI agents, and other applications to read and write SEO metadata programmatically for posts, pages, and WooCommerce products.
Features:
<ul>
<li>Rank Math SEO Support — Full access to all Rank Math meta fields</li>
<li>Yoast SEO Support — Full access to all Yoast SEO meta fields</li>
<li>WooCommerce Compatible — Works with product post types</li>
<li>Secure — Requires WordPress Application Password and edit_posts capability</li>
<li>Auto-Detection — Automatically detects which SEO plugin is active</li>
<li>Status Endpoint — Dedicated API endpoint for plugin and SEO detection</li>
<li>Zero Configuration — Works out of the box after activation</li>
</ul>
REST API Endpoints:
<ul>
<li><code>GET/POST /wp-json/airano-mcp-seo-bridge/v1/posts/{id}/seo</code> — Post SEO data</li>
<li><code>GET/POST /wp-json/airano-mcp-seo-bridge/v1/pages/{id}/seo</code> — Page SEO data</li>
<li><code>GET/POST /wp-json/airano-mcp-seo-bridge/v1/products/{id}/seo</code> — Product SEO data (WooCommerce)</li>
<li><code>GET /wp-json/airano-mcp-seo-bridge/v1/status</code> — Plugin status and SEO detection</li>
</ul>
Designed for <a href="https://github.com/airano-ir/mcphub" rel="nofollow ugc">MCP Hub</a> — the AI-native management hub for WordPress and self-hosted services.

Airano MCP SEO Meta Bridge

Exposes Rank Math SEO and Yoast SEO meta fields via WordPress REST API for use with MCP servers and AI agents.

Botailor ModelContext Integrator for AI vs Airano MCP SEO Meta Bridge