Skip to main content
Glama
deenesjakoruzh
runbookai

Runbook

Official
by runbookai
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Runbook MCP Server

Runbook MCP Server enables you to run your own runbooks from Claude Desktop.

  • Run ops runbooks (e.g., deploy a service, upgrade a Kubernetes cluster)

  • Run manual test plans (e.g., create a new EC2 instance, ssh into the instance, and run the integration test there).

Please watch the demo video below to understand how it works!

demo

How to Use

Step 1. Start the MCP server with Claude Desktop.

Create config.yaml

Put the following configuration to claude_desktop_config.json.

{
  "mcpServers": {
    "runbook": {
      "command": "uv",
      "args": [
        "--directory",
        "<ABSOLUTE_PATH>/runbook-mcp-server",
        "run",
        "runbook_server.py"
      ]
    }
  }
}

Related MCP server: MCP Server Generator

Step 2. Create runbooks

You can use markdown files or text files as runbooks. See examples.

We support env/var substitution.

Define env.yaml.

env:
  key: value

  • {env[key]} is replaced with value.

  • {var.name} is replaced with a variable value.

Rebuild the index when files are updated.

You can also create a new runbook, use the create_runbook tool. Here is an example prompt:

Example 1

Create a new runbook:

- name: list_pods
- content: List pods in all namespaces, find pods that are not ready, and send that to Slack.

You don't need to interpret the content. Please just pass it to the tool.

Step 3. Run runbooks

To run a runbook, take the following steps:

  1. Click "Attach from MCP" from Claude Desktop.

  2. Select get_runbook_as_prompt from the list of integrations.

  3. Pass the name of the runbook you would like to execute. Also specify variables with a comma-separated list (e.g., var1=key1,var2=key2).

  4. Submit the generated prompt.

Then Claude Desktop will talk to other MCP servers to run the runbook.

Example MCP Servers that can be used to Run Runbooks

Development Plan

  • Instead of saving the content of the runbook in the database, just save as a file. This helps easy editting. People can also simply use GitHub for versioning.

  • Runbook template X that is instantiated with given inputs.

    • Maybe this is not needed. A user just needs to put additional prompts when running the runbook.

  • Save executing log (for auditting and refinement)

    • Remove secrets

    • Also pass a past log to the runbook prompt if this helps better execution

  • Approval flow.

    • Add a tool request_approval.

    • This sends a slack message to a channel.

    • Then the Runbook MCP server watches the channel. If someone responds (yes / no), it proceeeds or returns an error.

  • Better runbook search

    • The exact name match is not great

  • Registrtation to Smithery.

Potential Work Items where its Feasibility is not clear

Note: Claude Desktop does not support "Sampling". This puts some limitations.

  • Sub-runbook and reusable execution block

  • Rest endpoint + frontend for managing runbooks.

  • Be able to edit the runbook (with versioning)

  • show an execution plan for runbook X (dry-run)

    • Restrict MCP servers and tools

  • convert a previous conversation into a runbook

  • fine-tuning.

  • Be able to refine a runbook. If there is a successful execution, save it as an example and give it to Claude.

  • Periodic execution

  • Be able to provision an environment (VM, docker) for running MCP servers.

Available Tools

2 tools
create_runbookD
ParametersJSON Schema
NameRequiredDescriptionDefault
contentYes
nameYes

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

delete_runbookD
ParametersJSON Schema
NameRequiredDescriptionDefault
nameYes

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv1.0.0
    • First observedcreate_runbook
    • First observeddelete_runbook
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.8/5.0
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.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • my-mcp-server

    15972289829
    F
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that allows integration with Claude Desktop by creating and managing custom tools that can be executed through the MCP framework.
    88
    -

  • MCP Server Generator

    SerhatUzbas
    F
    license
    Not graded
    quality
    F
    maintenance
    Creates, manages, and registers custom MCP servers for Claude Desktop. Enables users to generate and configure new MCP servers through natural language.
    11
    -

  • Expose

    deadcodedump
    A
    license
    Not graded
    quality
    C
    maintenance
    Easily build MCP tools for Claude desktop app.
    132
    21
    MIT

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/runbookai/runbook-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server