thorbit-wordpress-mcp

The WordPress specialist MCP for Thorbit. It ships three deliberately separate MCP executables:

• thorbit-wordpress-mcp is the hosted organization-scoped content and builder surface.
• thorbit-wordpress-developer-mcp is a local, owner-only application-control surface backed by Agency Bridge's separately enrolled Ed25519 signer.
• thorbit-wordpress-site-mcp is the direct local connector for ordinary Agency Bridge content, SEO, schema, media, builder, recovery, site-admin, and LLMS discovery operations. It uses local site aliases and the Bridge credential already held in Keychain; it does not route page work through Thorbit's hosted API.

Direct local Agency Bridge MCP

npx -y -p thorbit-wordpress-mcp@latest thorbit-wordpress-site-mcp

The connector builds its deterministic capability-family schemas from the installed thorbit-wordpress operator contract and refuses to start when the operator contains an unassigned or unavailable ordinary operation. Every call names the local site alias and passes a strict fixed operation request. Unknown or accepted-unverified writes retain their original private input for the read-only reconcile tool; the connector never replays an ambiguous mutation.

Page-level Schema.org JSON-LD is a first-class document: read its revision, then replace the raw JSON-LD object or array with the exact revision and a stable idempotency key. Agency Bridge creates a snapshot, purges page caches, and returns independently verified readback. Do not embed schema script tags in Elementor HTML.

LLMS discovery stays autonomous in Agency Bridge after setup. Use wordpress_llms_read for llms-status, llms-config-get, and llms-validate. Use wordpress_llms_apply for the idempotent llms-config-update, llms-refresh, and llms-rollback operations. Read status and config before a change. Configuration and rollback require their exact returned guards, and an unknown or accepted-unverified mutation must go through wordpress_change_reconcile; never resend it. Enabling, disabling, or changing robots discovery alters the public site, while MCP availability is not required for subsequent automatic refreshes.

Run

THORBIT_API_KEY=your_key npx -y thorbit-wordpress-mcp@latest

By default the server connects to https://thorbit.ai. Set THORBIT_BASE_URL only when Thorbit support directs you to another hosted origin.

The WordPress site's owner controls advanced access in WordPress under Settings → Agency Bridge. Dangerous file operations remain bounded by the plugin contract and are unavailable unless that access is enabled.

Local owner developer MCP

The developer MCP lets an MCP client invoke the existing signed Agency Bridge developer API without controlling a browser. It exposes developer status, fixed read operations, guarded file/option/extension mutations, explicit fresh-read reconciliation of unfinished mutations without replaying the write, auditable supersession of aged ambiguous builder attempts, verified source exports, and encrypted full-site development clones. A development clone contains the complete WordPress application tree, including empty directories, and a frozen binary-safe SQL dump, then is decrypted and hash-verified only beneath the configured local output root. It never accepts an arbitrary REST route or a production restore target.

THORBIT_WORDPRESS_DEVELOPER_OUTPUT_ROOT=/private/wordpress-exports \
  npx -y -p thorbit-wordpress-mcp@latest thorbit-wordpress-developer-mcp

By default it uses the site profiles and macOS Keychain signer maintained by the installed thorbit-wordpress operator. THORBIT_WORDPRESS_OPERATOR_PATH may select another absolute installation of that operator. Export callers pass a single safe child-directory name; the MCP refuses destinations outside THORBIT_WORDPRESS_DEVELOPER_OUTPUT_ROOT and returns receipts and artifact paths instead of placing large site bytes in the MCP response.

Complete development-clone exports may run for up to one hour. If the client process is interrupted after the export ID is checkpointed, call the same export tool with the same directory and resumeExportId; the MCP reuses the destination-bound private recipient key and completed encrypted chunks instead of creating a second server export.

Mutation inputs are retained as private files only while the local result is accepted_unverified or unknown. The reconcile tool requires the exact operation ID and byte-identical request, invokes the operator's read-only reconciliation path, and removes the retained input after a terminal result.

This local executable is intentionally not mounted behind Thorbit's public hosted API credential. Enabling it does not change the authority of existing content MCP clients.

The supersede tool is a local recovery operation, not a WordPress edit. It requires the exact pending operation and input hash, a fresh exact builder revision, a written owner reason, and acknowledgeAmbiguousWrite: true. It archives the unresolved history before releasing the lock and never claims that the interrupted historical write did or did not execute.

Release notes are published with the Thorbit Phoenix releases.