Picot MCP
Picot MCP turns your WordPress site into an MCP (Model Context Protocol) server so AI clients such as Cursor or Claude Code can work with content safely. Architecture: the official WordPress MCP Adapter is the protocol runtime; Picot adds the product layer (API keys, scopes, admin UI, audit log). On
About this tool.
Picot MCP turns your WordPress site into an MCP (Model Context Protocol) server so AI clients such as Cursor or Claude Code can work with content safely.
Architecture: the official WordPress MCP Adapter is the protocol runtime; Picot adds the product layer (API keys, scopes, admin UI, audit log).
- One MCP URL and API keys to connect (plaintext shown only once at issue)
- Multiple API keys with per-key scopes, optional expiry, and rate limits
- Feature toggles for core WordPress areas plus optional Picot product integrations (SEO Writer, AIO Optimizer, Editor Converter)
- Plugin/theme install and update from wordpress.org slugs only
- Plugin/theme activation, deactivation, and ZIP package transfer are not available via MCP (use WordPress admin)
- Audit log with user, key id, IP, and failure codes
- Built on the WordPress Abilities API and official MCP Adapter
Getting started.
- 01Upload the picot-mcp folder to /wp-content/plugins/
- 02Activate the plugin through the Plugins screen
- 03Open Settings → MCP, enable the server, review the site ceiling, issue an API key, and copy the key immediately (it cannot be shown again)
Frequently asked questions.
Does this plugin need Composer on the site?
No. Release packages already include the required MCP Adapter under vendor/ .
Who can manage API keys?
Only administrators ( manage_options ).
What is the default MCP endpoint?
New installs use /wp-json/picot-mcp/mcp-server with MCP disabled until you enable it. Existing sites keep their previously saved route until changed in Settings.
