gapify-mcp-server
Related Servers
Alternatives to gapify-mcp-server
No user-submitted related servers found.
Related Servers
- 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

FirstReply MCP Serverofficial
AlicenseBqualityCmaintenanceExposes FirstReply customer support operations as MCP tools, enabling AI assistants to browse conversations, draft replies, manage API keys, and access support statistics.841MIT- FlicenseNot gradedqualityDmaintenanceEnables interaction with the Gorgias helpdesk API, providing tools to manage tickets, customers, and other helpdesk functionalities through natural language.4-
- AlicenseCqualityDmaintenanceMCP server that exposes the complete Libredesk REST API (54 endpoints) as tools, enabling natural language management of conversations, contacts, agents, teams, and more for the open-source customer support desk.5410 npm4MIT
- FlicenseNot gradedqualityCmaintenanceEnables an AI to perform customer support workflows by looking up customers, retrieving orders, and creating support tickets through MCP tools.2 npm-
- AlicenseCqualityCmaintenanceProvides AI assistants with access to all public GoHighLevel API endpoints as MCP tools, enabling contact, conversation, opportunity, calendar, and other CRM operations with configurable safety gates for writes and deletes.5567 npm2MIT
TDQS
Scored across 118 tools
Descriptions indicate auth surface and path, but the set contains multiple near-duplicate pairs across platform, account, and client APIs (e.g., gapify_platform_list_agent_bots vs gapify_list_agent_bots; gapify_create_contact vs gapify_client_create_contact), so an agent can easily select the wrong variant. The descriptions help, but the sheer number of overlapping resources keeps ambiguity present.
Names consistently use snake_case and a gapify_ prefix, but verb conventions vary across resources—create vs add (create_agent_bot vs add_agent), delete vs remove (delete_contact vs remove_agent), and set/toggle for state changes—making the pattern only partially predictable.
118 tools is far beyond the recommended 3-15 range and exceeds the rubric's 50+ threshold for extreme mismatch. Even for a large platform API, this volume overwhelms tool selection and context handling.
The set covers CRUD for most major resources (accounts, users, agents, teams, inboxes, contacts, conversations, messages, labels, custom attributes, filters, webhooks, automation rules, help center, integrations, reports) and includes a raw_request escape hatch. Some lifecycle operations (e.g., updating or deleting conversations) are absent, but they are workable via raw requests.