@theyahia/jivosite-mcp
Related Servers
Alternatives to @theyahia/jivosite-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables interacting with Bitrix24 CRM via webhook API, offering tools for deals, contacts, tasks, users, files, and messaging.1244 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables language models to interact with Bitrix24 CRM, providing tools to manage deals, leads, contacts, tasks, activities, users, files, chat messages, and live chat sessions.3 npm1-
- FlicenseAqualityDmaintenanceIntegrates the Tidio customer service platform with LLMs, enabling management of conversations, contacts, tickets, and operators through natural language.163-
- FlicenseNot gradedqualityDmaintenanceEnables interaction with VTiger CRM through tools for module listing, CRUD operations, querying, and searching records.1-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with WhatsApp Business tools and services through a unified API.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Intercom's customer communications platform via the Intercom REST API, providing 102 tools for managing admins, articles, companies, contacts, conversations, and more.2MIT
TDQS
Scored across 11 tools
Most tools target distinct resources (chats, agents, contacts, webhooks), but get_chats and skill_active_chats overlap in purpose (both deal with active chats), and get_agents and skill_agent_stats have overlapping focus on agents. The 'skill_' tools appear to provide summaries that could be confused with the base getter tools, though descriptions help differentiate them.
The majority of tools follow a consistent verb_noun pattern (get_chats, create_contact, send_message, etc.). However, two tools have a 'skill_' prefix (skill_active_chats, skill_agent_stats), which deviates from the established pattern and introduces a mixed convention.
With 11 tools, the set is well-scoped for a JivoSite integration. Each tool serves a clear purpose in managing chats, contacts, agents, and webhooks, fitting comfortably within the typical 3-15 range without feeling sparse or bloated.
The surface covers core operations: listing and messaging chats, managing contacts (get/create but no update/delete), retrieving agents, and CRUD for webhooks (get/create/delete but no update). Minor gaps exist (e.g., no chat close/assign, no contact update) but agents can likely work around them for common workflows.