Terms used across this knowledge base, defined plainly.
- Application Password
- A 24-character token you generate in WordPress (Users → Profile → Application Passwords) that lets a tool authenticate to your site without using your main wp-admin password. Scoped, revocable, and bypasses 2FA by core WordPress design.
- Cowork
- Anthropic’s desktop assistant mode that lets Claude run plugins on your computer. WordPress for Cowork is one such plugin.
- Cowork Bridge
- The WordPress half of WordPress for Cowork — a plugin you install on your WordPress site (
cowork-bridge.zip) that adds the MCP endpoint at/wp-json/coworkmcp/v1/mcp. - License key
- Your CW- formatted purchase key (e.g.,
CW-XXXXXX-XXXXXX-XXXXXX). Lives in your My Account page after purchase. Used during/wp-setup. - Machine ID
- A short identifier Cowork uses to track which device a license is active on. Used to enforce the 2-device cap. Not personally identifying.
- MCP (Model Context Protocol)
- The open protocol Cowork uses to talk to plugins. WordPress for Cowork’s MCP endpoint at
/wp-json/coworkmcp/v1/mcpis what Cowork on your desktop sends requests to. - mu-plugin
- “Must-use” plugin. Lives in
wp-content/mu-plugins/and is always active — no separate activation step in wp-admin. Cowork Bridge deploys its core endpoint and tool-interceptor as mu-plugins. - Pairing
- The trust relationship between Cowork on your desktop and Cowork Bridge on your WordPress site. Created by
/wp-setup. Stored locally on both sides. - REST API
- WordPress’s built-in HTTP interface for reading and writing site data. WordPress for Cowork uses it. Lives under
/wp-json/. - Seat
- One user license. Solo = 1 seat. Agency = 5 seats. Enterprise = per-seat, minimum 6. Sites are unlimited; seats are the constraint.
- Slash command
- A command you type in Cowork starting with
/, like/wp-statusor/wp-backup. Shortcut for common workflows. - Snapshot
- A full-site backup taken by
/wp-backup. JSON file stored on your own server in a folder protected by.htaccess.