A
licenseNot graded
qualityB
maintenanceEnables AI clients to list, inspect, triage, and update support tickets via MCP tools, with a mocked dataset designed for swapping in real ticket sources later.
MIT
mcp-app-harness
by tachyurgy
Related Servers
Alternatives to mcp-app-harness
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to investigate production incidents by exposing service health, logs, and deployment data through MCP tools.15 npm-
- AlicenseNot gradedqualityBmaintenanceA simulated CloudOps MCP server exposing tools, resources, and prompts backed by fake Azure-style infrastructure data to demonstrate AI-driven operational workflows without real credentials.MIT
- FlicenseNot gradedqualityBmaintenanceEnables a helpdesk MCP server for a fake company, allowing ticket management, issue tracking, and employee directory lookups through natural language.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and software engineers to investigate and resolve realistic distributed-system incidents using safe MCP-based diagnostic tools for code, logs, metrics, traces, database, and deployments.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceDeploys a Model Context Protocol (MCP) server on Azure with industry-specific templates, sample data, and pre-configured tools for AI agents to query and manage resources.1MIT
TDQS
C2.8/5.0
Scored across 8 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: ticket tools (create, read, update status, list) and state management tools (populate, restore, snapshot) operate on different aspects with no overlap.
Naming Consistency4/5
Ticket tools follow consistent verb_noun pattern (e.g., create_ticket), but state management tools use single-word verbs (populate, restore, snapshot), creating a minor inconsistency in naming conventions.
Tool Count5/5
8 tools is well-scoped for a ticket system with testing utilities; each tool earns its place without being excessive or insufficient.
Completeness3/5
Core ticket lifecycle is covered (create, get, list, assign, close), but missing update for other fields (e.g., priority, description) and no reopen functionality, leaving notable gaps.
Maintenance
ActivityInactive
ResponsivenessNo issues