tessera-mcp
Related Servers
Alternatives to tessera-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables secure support-ticket and customer-account operations with signed JWT authentication, prompt-injection and tool-poisoning guardrails, and human-in-the-loop confirmation for destructive actions.MIT
- AlicenseNot gradedqualityAmaintenanceExposes a fictional small business as 46 MCP tools spanning CRM, inbox, calendar, invoicing and phone, letting agents read and modify customers, deals, messages and payments with validated, audited writes that stay inside the process.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceExposes a support-ticket inbox as tools an AI client can use to list, inspect, triage, and update tickets, including LLM-based category, priority, and sentiment classification with a drafted first response informed by similar past tickets. It works with a mocked dataset styled after a home-loan partner-support inbox, with the tool interface designed so a real ticket source could be swapped in later.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to securely call enterprise MCP tools with tenant-scoped RBAC, human approvals, audit logging, and multi-tool workflows across customer, order, document, and ticket data.-
- FlicenseBqualityCmaintenanceEnables LLM agents to operate a CRM through 114 typed tools across 24 modules, covering contacts, pipelines, calendars, messaging, invoicing, and payments. Destructive and outward-facing actions are annotated for visibility and approval.114-
- FlicenseNot gradedqualityCmaintenanceEnables SaaS support desk operations with sixteen tools for customer lookup, invoice and ticket access, refunds, and admin actions, organized into four risk tiers.-
TDQS
Scored across 7 tools
Each tool targets a distinct resource and action: tickets, customers, invoices, and trial management. No two tools overlap in purpose; daily_summary aggregates but does not duplicate list_open_tickets.
Most tools follow a clear verb_noun pattern (list_open_tickets, get_customer, update_ticket_status). The outlier is daily_summary, which uses a noun phrase rather than a verb, creating a minor inconsistency.
With 7 tools, the server is well-scoped for a support and billing domain. Each tool covers a distinct function without bloat or redundancy.
The tool set covers ticket status updates, customer lookups, invoice search, refunds, and trial extensions. Minor gaps exist, such as no way to list closed tickets or update customer details, but these are not essential to the core workflow.