Skip to content

MCP 0.4.2 / Overview

MCP overview

Connect approved MCP clients to permission-aware Social Terminal tools.

MCP

MCP exposes reviewed Social Terminal capabilities to compatible clients without turning WordPress into an unrestricted remote command console. Every tool is registered by its owning add-on, classified by risk, checked against the current actor, and blocked unless an explicit server policy allows it.

Two connection surfaces

The administrator/operator server is the Free baseline. It supports health checks, inventories, and approved operator workflows configured by a trusted site administrator.

MCP Pro adds registered-user connections through OAuth with PKCE. Administrators must explicitly enable user connections. Users can review scopes, approve a client, see connected applications, and revoke access. Anonymous connections are never allowed.

Free and Pro

Free provides the administrator health surface, safe read-only inventory, product and command discovery, diagnostics, and the reviewed operator endpoint.

Pro enables per-user OAuth/PKCE connections, connected-app management, user endpoints, approval history, and eligible command execution for the authenticated WordPress user. Disabling Pro or the site switch removes user routes without silently deleting saved configuration.

Remote-command policy

The add-on that owns a command also owns its remote policy. Unknown commands fail closed. Read-only tools may run when the connection and actor have the required scope. Sensitive or mutating actions require the exact owning capability and may also require a short-lived, one-time browser approval. MCP never converts a client request into broader WordPress authority.

Shortcode rendering and other presentation-oriented commands remain blocked from frontend MCP until they have a dedicated server-safe contract.

Privacy and revocation

Tokens are scoped, revocable, and associated with one actor. OAuth uses PKCE and exact redirect validation. Status surfaces avoid credentials and private command payloads. Removing a connection invalidates its future access; it does not delete the user's WordPress account or the owning add-on's data.

Start here

Install and test the administrator server, then use the operator and connection guide before enabling registered-user MCP connections.

Was this documentation helpful?Your response helps us improve this page.