ops-platform-mcp
Related Servers
Alternatives to ops-platform-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA dead simple MCP server for exposing your app functions to AI agents like Claude Desktop.6 npm6MIT
- FlicenseNot gradedqualityDmaintenanceDemonstration MCP server for Claude Team integration, enabling querying of sample business data (orders, clients, products) and real-time currency exchange rates through natural language.-
- AlicenseBqualityDmaintenanceMCP server for managing Claude Code conversation sessions1258 npmMIT
- FlicenseNot gradedqualityDmaintenanceAn OAuth-authenticated MCP server that bridges Claude AI with a task management system, allowing users to list, create, and update tasks through natural language commands.1-
- AlicenseBqualityBmaintenanceMCP server for integrating Actual Budget with Claude and other LLM assistants.17328 npm236TypeScriptMIT
- AlicenseAqualityCmaintenanceLocal MCP server that wraps the headless Claude Code CLI as MCP tools, providing stateless access to Claude's coding capabilities through prompt-based interactions. It enables users to execute Claude Code commands with various prompt formats and structured outputs directly from MCP clients.3MIT
TDQS
Scored across 8 tools
Each tool has a distinct purpose covering tasks, projects, employees, and time tracking. There is no overlap; for example, create_task and update_task_status are clearly separate, and list_tasks is different from list_projects or list_employees.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_task, get_project_hours, list_employees). No mixing of conventions or inconsistent verb styles.
With 8 tools, the count is well-scoped for an operations platform covering task management, project tracking, employee lookup, and time logging. Each tool serves a necessary function without bloat.
The set covers core operations (create, read, update status, list, log time, report), but lacks an update tool for task fields other than status (e.g., assignee, due date) and no delete tool. This creates a notable gap in task lifecycle management.