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 gradedqualityCmaintenanceEnables an AI assistant to safely read and write small-business ERP data such as customers, appointments, invoices and bills, gated by OAuth 2.1, role-scoped tool registration, preview-and-confirm write approvals, masked personal data and an audit trail. Runs against an in-memory mock ERP with synthetic data so the safety patterns can be tried out immediately.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
- AlicenseNot gradedqualityBmaintenanceEnables agents to browse a demo menu and call ordering, discount, and refund tools with safeguards including rate limiting, audit logging, signed receipts, policy checks, and prompt-injection scanning.3Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables read- or write-scoped access to synthetic enterprise orders, inventory, support tickets, and metrics via schema-validated JSON-RPC tools over stdio and HTTP, with permission allow-lists and audit logging. It also exposes enterprise resources and prompt templates for grounded, cited, multi-step assistant workflows.MIT
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.