A
licenseC
qualityB
maintenanceEnables Claude Code to read, edit, and manage WordPress pages, posts, shortcodes, and media via the WordPress REST API.
80
13 npm
3
MIT
Zuar Portal Blocks MCP Server
Related Servers
Alternatives to Zuar Portal Blocks MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables Claude to design and build interactive 3D games within the Portals virtual platform through direct API integration. It facilitates automated asset placement, interaction logic configuration, and quest management using natural language commands.4-
- FlicenseAqualityCmaintenanceEnables Claude to read context, create, and edit pages on WordPress sites via the REST API using Application Passwords.6-
- AlicenseAqualityCmaintenanceEnables direct interaction with WordPress sites via Claude using the REST API, allowing reading, creating, updating, and deleting content securely with application passwords.20MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude to interact with Qlik Cloud applications and extract data from visualizations through the Qlik Cloud API.11MIT
- AlicenseBqualityCmaintenanceConnects 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.4721 npm22MIT
TDQS
A4/5.0
Scored across 17 tools
Disambiguation4/5
Most tools target distinct resource/action pairs, and list_resource, find_resource, and describe_resource are clearly separated by purpose. The main ambiguity is between score_portal and validate_portal, both of which audit portal health, but their descriptions distinguish scoring from structural validation.
Naming Consistency4/5
Almost every tool follows the imperative verb_noun pattern: validate_block, list_resource, find_resource, execute_query, snapshot_portal, etc. The outlier is 'naming', which is a noun rather than a verb phrase and internally multiplexes suggest/parse actions, breaking the otherwise predictable pattern.
Tool Count3/5
At 17 tools, the server sits in the borderline-heavy range, though the breadth of portal management topics partly justifies it. Each tool has a distinct role, but the count is high enough that an agent must work harder to select among them.
Completeness2/5
The tool descriptions repeatedly reference create_block/update_block, create_resource/update_resource, get_resource, and delete_resource, but none of those tools are actually exposed. This leaves significant gaps: an agent can validate and list resources but cannot perform general create, update, or single-resource get operations.
Maintenance
ActivitySlowing
ResponsivenessNo issues