=== Birlo Bridge Lite ===
Tags: mcp, ai, automation, oauth, wordpress
Requires at least: 6.4
Tested up to: 7.1
Requires PHP: 8.0
Stable tag: 1.2.1
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Connect WordPress to MCP-compatible AI assistants using OAuth, granular scopes, WordPress capabilities, approvals and audit logs.

== Description ==

Birlo Bridge Lite is a self-hosted MCP (Model Context Protocol) server for WordPress.

The Lite edition exposes a deliberately limited set of tools for site information, pages, posts, media, revisions, audit history and approval status.

Birlo Bridge Lite does not include plugin management, theme/plugin file management, arbitrary administrative REST requests, WooCommerce administration, appearance editing, site identity editing, form integrations or builder integrations. Those capabilities, when installed, are provided by separate add-ons.

= Security model =

* OAuth Authorization Code with PKCE S256.
* Dynamic client registration is closed by default and requires a short administrator-opened pairing window.
* Each pairing window can register one client.
* Granular OAuth scopes for site, content and media access.
* WordPress capability checks for every tool, including per-object checks where applicable.
* 15-minute access tokens.
* Rotating single-use refresh tokens with a maximum 30-day lifetime.
* Refresh-token replay detection and token-family revocation.
* OAuth and MCP rate limiting.
* Sensitive and non-explicitly-read-only operations require individual secondary approval in wp-admin.
* Approval handling fails closed for unknown or newly added tools.
* Remote media import is restricted to HTTPS and protected against private/reserved network access.
* Audit logging for security-relevant activity.
* No arbitrary shell or WP-CLI access.
* No Lite file-management access to plugin/theme files or wp-config.php.

The MCP endpoint is:

/wp-json/birlo-bridge/v1/mcp

= Privacy and external services =

Birlo Bridge Lite runs on your own WordPress site. The plugin does not automatically send site content to Birlo. Data is returned only when an authenticated MCP client authorized by the WordPress administrator calls an exposed tool.

Your chosen MCP or AI client may process information that you authorize it to request. Review that service's privacy policy before connecting it.

= Optional add-ons =

Separate add-ons can extend Birlo Bridge Lite with additional capabilities. The Lite plugin remains functional without them.

== Installation ==

1. Install and activate Birlo Bridge Lite.
2. Open Tools > Birlo Bridge.
3. Open the OAuth pairing window when you are ready to connect a client.
4. Connect your MCP-compatible client.
5. Review requested scopes.
6. Approve sensitive operations individually when prompted.

== Frequently Asked Questions ==

= Does Birlo Bridge Lite require a Birlo account? =

No. Lite is self-hosted.

= Does it give an AI full server access? =

No. Lite exposes only its registered MCP tools and requires OAuth scopes plus WordPress capability checks.

= Does Lite manage plugins or arbitrary plugin/theme files? =

No.

= Does Lite include WooCommerce administration? =

No.

= Can I revoke a connection? =

Yes. OAuth connections can be revoked from WordPress.

= Which actions require secondary approval? =

Any operation that is not explicitly declared read-only is treated as sensitive and requires individual approval. Unknown or newly added tools fail closed.

== Changelog ==

= 1.2.1 =
* Reduced the WordPress.org package to Lite-only runtime capabilities.
* Removed manual bearer-token authentication.
* Added granular OAuth scopes and WordPress capability checks.
* Added one-use OAuth pairing windows and stricter redirect URI validation.
* Added short-lived access tokens, rotating single-use refresh tokens and replay detection.
* Added OAuth endpoint rate limiting and token-family revocation.
* Made secondary approvals fail closed for unknown or non-explicitly-read-only tools.
* Added per-object revision permissions.
* Hardened remote media URL imports against SSRF and private/reserved networks.
* Removed stale premium capability declarations and documentation from Lite.

= 1.2.0 =
* Initial modular release.

== Upgrade Notice ==

= 1.2.1 =
Security hardening release. Existing legacy OAuth clients may need to reconnect with granular scopes.
