manifest / integrations / mcpconnector
AmphiBee MCP Connector
Exposes WordPress content management as Model Context Protocol tools, with a built-in OAuth 2.1 provider so remote clients such as Claude can connect to the site.
★ 0stars
23composer installs
0forks
Install
The author publishes release zips, so WP-CLI can install straight from GitHub:
wp plugin install https://github.com/pollora/mcpconnector/releases/download/v1.2.2/mcp-connector-v1.2.2.zipAlso on Packagist as pollora/mcp-connector:
composer require pollora/mcp-connectorFrom the readme
MCP Connector
Exposes WordPress content management as Model Context Protocol
tools, with a built-in OAuth 2.1 provider so a remote client such as Claude can
connect to the site by URL.
The plugin is deliberately generic: nothing in it is specific to one site. What
it publishes is configurable, what it refuses is enforced in two independent
layers, and the ability set is extensible through a filter.
What it gives a client
27 first-class MCP tools, each with its own input schema and behaviour
annotations, grouped into six sets that can be switched on and off
independently:
| Group | Tools |
|---|---|
| Posts and pages | get-posts, get-post, get-pages, create-post, update-post, delete-post, set-post-terms |
| Taxonomies and terms | get-taxonomies, get-terms, create-term, delete-term |
| Media library | get-media, upload-media-from-url, update-media, set-featured-image, delete-media |
| Navigation menus | get-menus, get-menu-items, get-menu-locations, create-menu, add-menu-item, update-menu-item, delete-menu-item, assign-menu-location |
| Users (off by default) | get-users, get-user |
| Site information | get-site-info, get-post-types, update-option |
get-posts filters by any tax
Read the full README on GitHub →