pachatraining-mcp
Related Servers
Alternatives to pachatraining-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code and other MCP clients to interact with Microsoft SQL Server databases through standardized tools for query execution, schema exploration, table management, and stored procedure execution.94 npm1MIT
- FlicenseAqualityDmaintenanceEnables querying, exploring, and interacting with Azure SQL databases through MCP-compatible clients like Claude Desktop.5-
- AlicenseNot gradedqualityDmaintenanceProvides secure SQL Server database access, allowing users to list tables and execute SQL queries through natural language in Claude Desktop.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for Microsoft SQL Server integration that enables users to query, monitor, and analyze databases directly through Claude. It supports schema exploration, performance analysis, and optional write operations via natural language commands.7 npm1MIT
- AlicenseBqualityDmaintenanceEnables AI agents to interact with Microsoft SQL Server databases via MCP, supporting table listing, schema retrieval, and CRUD operations.31MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that exposes SQL Server databases to Claude, allowing natural language queries with tools to list tables, describe schemas, and run read-only SELECT statements.-
TDQS
Scored across 8 tools
Each tool targets a distinct resource and action: weekly session listing, single-session detail, trainer load, unpaid invoices, at-risk sessions, cancelled enrollments, and two mutations. The only mild overlap is between sessions_in_week and sessions_to_watch, but their filters (all sessions vs planned/open under half full) are clearly spelled out, and descriptions cross-reference each other to avoid misselection.
Names are uniformly snake_case with a readable convention: read/query tools use noun phrases (sessions_in_week, trainer_load, unpaid_invoices) and mutations use verb_noun (postpone_session, cancel_enrollment). The read-vs-write split is intentional and consistent, though the mixed style is a minor deviation from a single verb_noun pattern.
Eight tools is well-scoped for a training-administration server: each covers a distinct workflow (session lookup, detail, trainer billing, invoices, watchlist, cancellations, postpone, cancel enrollment) with no filler. Nothing feels redundant or missing from a count perspective.
The surface covers read access across sessions, enrollments, trainers, and invoices, plus two correction operations. However, obvious lifecycle gaps remain: no tool to create a session or enrollment, no way to mark a session completed/cancelled, and no invoice payment/settlement operation, which will force agents to hit dead ends for common administrative tasks.