Search

RADMCP for Plugin Developers

THE OPEN CONNECTOR FOR WORDPRESS PLUGINS

Your plugin can speak MCP without becoming an MCP server.

Add a compact integration layer, keep your plugin's domain logic, and let RADMCP provide the secure connection that AI agents understand.

CONNECTOR 1.0.0

Dependency-free PHP

✓ Namespaced tool registration

✓ WordPress capability gates

✓ Strict JSON Schema inputs

✓ Safe, bounded outputs

THE SHARED INFRASTRUCTURE

A secure contract between your plugin and the agent.

The connector normalizes how tools are declared. RADMCP then exposes only integrations that are installed, active, registered, and explicitly enabled by the site owner.

NAMESPACE

Collision-resistant tools

Every tool belongs to your plugin's namespace. Duplicate plugin IDs and tool names are rejected before they can create ambiguous behavior.

SCHEMA

Predictable arguments

Object-shaped schemas reject undeclared fields and enforce types, lengths, ranges, enums, URLs, nesting depth, and payload complexity.

BOUNDARIES

Contained execution

Exceptions are contained, outputs are size-limited, sensitive keys are redacted, and unsafe object or resource returns are blocked.

CLEAR RESPONSIBILITY

RADMCP handles the connection. Your plugin keeps authority.

The connector provides defense in depth. It never replaces the permission model your plugin already owns.

Use WordPress object-level checks, prepared SQL, safe HTTP APIs, sanitization, and escaping inside your handlers. Return site content as data—never as trusted AI instructions.

RADMCP owns

Authentication, plugin discovery, administrator enablement, global write controls, protocol handling, request limits, output redaction, and audit metadata.

Your plugin owns

Business rules, object ownership, record-level authorization, data validation, safe queries, remote destination allowlists, and the meaning of each operation.

SMALL INTEGRATION SURFACE

Register once. Appear automatically.

Load the connector from your main plugin file and register your integration on the provided WordPress hook. RADMCP detects it and adds it to the site owner's Plugin Access screen.

Open the complete example

use RADGroup\RADMCP\Connector\Connector;

Connector::register([

'id' => 'my_plugin',

'tools' => [ /* scoped tools */ ],

]);

SECURE BY DEFAULT

Guardrails developers do not have to rebuild.

Every tool needs a capability

The connector checks the declared WordPress capability immediately before invoking the handler.

Writes are explicit

Every tool declares whether it mutates state, and RADMCP separately requires the administrator's global write-tools setting.

Content stays untrusted

Descriptions, annotations, and output metadata reinforce that WordPress content may contain prompt injection and is never an instruction source.

APACHE-2.0 · FREE TO USE

Build the integration your users are already asking for.

Clone the repository, copy the source into your plugin, or install it through Composer from GitHub. The project includes documentation, an integration example, tests, PHP 8.1–8.4 CI, and private vulnerability reporting.

Secret Link