Kapiti MCP Server
Related Servers
Alternatives to Kapiti MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to publish and manage content on Inkwell sites via 12 tools, including inbox publishing, content management, and site configuration.1-
- AlicenseCqualityCmaintenanceEnables AI agents to manage WordPress sites with 190+ tools for content management, theme/plugin customization, file system operations, WooCommerce, and complete site control through natural language.10030 npm56MIT
- AlicenseNot gradedqualityBmaintenanceExposes the full Chatwoot API as 129 tools for AI assistants, enabling account, contact, conversation, message, inbox, team, report, help center, automation, and custom attribute management, plus exclusive Kanban and scheduled message features.6 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage WordPress sites via ~74 capabilities including content, media, plugins, themes, and more.-
- AlicenseCqualityDmaintenanceEnables AI agents to interact with Webflow APIs for managing sites, pages, components, CMS collections, and custom code.32877 npmMIT

Zarla MCP serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI assistants to build, edit, preview, and publish websites through natural language, including managing pages, designs, products, and site publishing.MIT
TDQS
Scored across 43 tools
The tools are generally well-differentiated by resource (e.g., content_site, staging_site, user, account) and action (e.g., get, create, update, delete), with clear boundaries. However, some tools like 'update_content_site' and 'update_staging_site' could be confused due to similar naming and overlapping domains, and 'health' and 'ping' are both diagnostic tools that might overlap in purpose.
The naming follows a highly consistent verb_noun pattern throughout, such as 'create_content_site', 'get_staging_site_page', and 'delete_user'. All tools use snake_case uniformly, with verbs like 'create', 'get', 'update', 'delete', 'upload', 'publish', and 'revert' applied predictably across resources, making the set easy to navigate.
With 43 tools, the count is excessive for the apparent domain of content and staging site management, user and account handling, and basic diagnostics. This high number suggests over-fragmentation, such as separate tools for logs and sections, which could overwhelm agents and reduce usability despite the comprehensive coverage.
The tool set provides complete CRUD/lifecycle coverage for all key domains: content sites, staging sites (including pages, sections, and files), users, and accounts. It includes advanced operations like publishing, reverting, uploading files, and diagnostics (health/ping), with no obvious gaps that would hinder agent workflows in this context.