DMTicket MCP Server
Related Servers
Alternatives to DMTicket MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceExposes seven read-only tools for sales engagement data from DM Faster, enabling agents to query workspace briefings, campaigns, sendings, replies, pipelines, and company timelines.Apache 2.0

Mailjet MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to interact with Mailjet's contact, campaign, segmentation, statistics, and workflow APIs for managing email marketing operations through natural language.123 npm11Apache 2.0- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage GoHighLevel workspaces through natural language, with 508 tools across 18 domains for complete CRM, marketing, and workflow automation.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage omnichannel CRM data (WhatsApp, Instagram, Facebook) via the official API, including leads, deals, pipelines, activities, tags, products, conversations, lists, attachments, and notes.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage Intercom support workflows, including searching and updating contacts, handling conversations, assigning and closing tickets, and logging notes.-
- AlicenseBqualityDmaintenanceEnables AI assistants to manage ActiveCampaign CRM, marketing automation, and contact data via 33 tools including contacts, deals, tags, automations, pipelines, custom fields, campaigns, accounts, and webhooks.6515 PyPI1MIT
TDQS
Scored across 155 tools
Many tools have overlapping purposes, e.g., 'create_a_contact' and 'contact_create' both create contacts. The naming is inconsistent, making it hard to distinguish between similar operations.
Tool names follow no consistent pattern, mixing 'contact_list', 'create_a_contact', 'get_details_of_a_contact', and 'contact_create' without rhyme or reason.
With 155 tools, the server is far too large for a typical MCP tool set. This excessive granularity undermines usability and suggests many tools could be merged or parameterized.
While the server covers many entities (contacts, conversations, agents, etc.), the massive redundancy and poor organization indicate significant gaps in coherent workflow coverage.