A
licenseNot graded
qualityC
maintenanceMCP server for authoring, validating, simulating, and publishing workflows for the Runbook workflow engine, including branch and run management.
MIT
Runbook
Officialby runbookai
Related Servers
Alternatives to Runbook
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityFmaintenanceCreates, manages, and registers custom MCP servers for Claude Desktop. Enables users to generate and configure new MCP servers through natural language.11-
- AlicenseNot gradedqualityDmaintenanceA local MCP server that connects Claude Desktop to execute custom local code, such as generating custom greetings.6 npmISC
- AlicenseNot gradedqualityCmaintenanceEasily build MCP tools for Claude desktop app.132 npm21MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that allows integration with Claude Desktop by creating and managing custom tools that can be executed through the MCP framework.75 npm-
- FlicenseNot gradedqualityDmaintenanceMCP server for integrating Rundeck with GenAI applications, enabling runbook automation and job scheduling through natural language.-
TDQS
D1.8/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct purposes: create_runbook for creating a runbook and delete_runbook for deleting one, with no overlap in functionality. This minimal set avoids any ambiguity, as each tool targets a specific, opposite action on the same resource.
Naming Consistency5/5
Both tools follow a consistent verb_noun pattern (create_runbook and delete_runbook), using snake_case and clear action verbs. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions.
Tool Count2/5
With only two tools, the server feels too thin for a runbook management domain, as it lacks essential operations like listing, retrieving, or updating runbooks. While the tools are well-defined, the count is insufficient for typical CRUD workflows, limiting agent capabilities.
Completeness2/5
The tool set is severely incomplete for runbook management, missing key operations such as get_runbook, list_runbooks, and update_runbook. This creates significant gaps that will cause agent failures, as users cannot retrieve or modify existing runbooks, leading to dead ends in workflows.