PressBridge
Related Servers
Alternatives to PressBridge
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables Claude and other MCP-capable agents to read a WordPress site and draft new posts through the WordPress REST API, with a read-only mode that disables write tools.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to manage WordPress sites through a self-hosted MCP endpoint, including content, media, plugins, themes, page-builder pages, SEO fields, plugin data, theme files, PHP snippets, and updates with approval controls.MIT
- FlicenseNot gradedqualityCmaintenanceEnables full WordPress operator access through Claude Code, including content, media, plugin/theme management, direct theme-file editing, backups, cache purging, and raw REST API calls, all secured with revocable tokens and no SSH requirement.1-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants and agents to communicate directly with a WordPress environment, executing PHP code and WP-CLI commands, inspecting and editing theme and plugin files in a sandbox, and managing posts, content, and Gutenberg blocks in real time.MIT
- AlicenseCqualityDmaintenanceEnables Claude Code to read, edit, and manage WordPress pages, posts, shortcodes, and media via the WordPress REST API.8012 npm3MIT
- AlicenseBqualityDmaintenanceConnects Claude to WordPress sites through the REST API, enabling AI-assisted content creation, publishing, media management, user administration, and site maintenance tasks through natural language.4723MIT
TDQS
Scored across 9 tools
Most tools are clearly separable by resource and action: file operations (list_dir, read_file, search, stat), site discovery (list_sites, wp_commands), and execution (wp). The only mild overlap is site_overview versus check_site_health, both framed as 'health' checks, though one is a data snapshot and the other a live boot probe.
Conventions are mixed: verb_noun (list_sites, list_dir, read_file, check_site_health), bare verbs/abbreviations (search, stat, wp), and noun phrases (wp_commands, site_overview). The wp/wp_commands pairing is internally coherent, but the set overall does not follow one predictable pattern.
Nine tools is well within the sweet spot for a WordPress inspection bridge. Each tool covers a distinct capability layer (site enumeration, filesystem, WP-CLI, health) without filler.
Read/inspect coverage is solid and wp provides a broad escape hatch for deeper WordPress operations. However, the filesystem surface is read-only (list_dir, read_file, search, stat) with no write/edit/delete counterpart, which is a notable gap if agents are expected to modify files.