de en es ja ko ru zh

Runbook

Name: Runbook
Author: runbookai

Official

by runbookai

Overview Schema Related Servers Score Discussions

Python

Hybrid

Runbook MCP 服务器

Runbook MCP Server 使您能够从 Claude Desktop 运行自己的运行手册。

运行操作手册（例如，部署服务、升级 Kubernetes 集群）
运行手动测试计划（例如，创建一个新的 EC2 实例，通过 ssh 进入该实例，然后在那里运行集成测试）。

请观看下面的演示视频以了解其工作原理！

如何使用

步骤 1. 使用 Claude Desktop 启动 MCP 服务器。

创建config.yaml

将以下配置放入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

步骤 2.创建 Runbook

您可以使用 Markdown 文件或文本文件作为 Runbook。请参阅示例。

我们支持 env/var 替换。

定义env.yaml 。

env:
  key: value

{env[key]}被替换为value 。
{var.name}被替换为变量值。

当文件更新时重建索引。

您还可以创建新的 Runbook，使用create_runbook工具。以下是示例提示：

示例 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.

步骤 3. 运行 Runbook

要运行 Runbook，请执行以下步骤：

在 Claude Desktop 中单击“从 MCP 附加”。
从集成列表中选择get_runbook_as_prompt 。
传递要执行的 Runbook 的名称。同时，请使用逗号分隔的列表指定变量（例如， var1=key1,var2=key2 ）。
提交生成的提示。

然后，Claude Desktop 将与其他 MCP 服务器通信以运行运行手册。

可用于运行 Runbook 的示例 MCP 服务器

GitHub
松弛
DesktopCommanderMCP
网络搜索和浏览器自动化（链接）
Kubernetes。有几种实现（例如mcp-k8s-go ）

发展计划

无需将 Runbook 的内容保存到数据库中，只需将其保存为文件即可。这有助于轻松编辑。此外，用户还可以直接使用 GitHub 进行版本控制。
使用给定输入实例化的 Runbook 模板 X。
- 也许这不是必需的。用户只需要在运行 Runbook 时添加额外的提示即可。
保存执行日志（用于审计和改进）
- 删除机密
- 如果这有助于更好地执行，还可以将过去的日志传递给运行手册提示
审批流程。
- 添加工具request_approval 。
- 这会向频道发送一条松弛消息。
- 然后，Runbook MCP 服务器会监视该通道。如果有人响应（是/否），则继续执行，否则返回错误。
更好的运行手册搜索
- 名字不太准确
注册至Smithery 。

可行性尚不明确的潜在工作项目

注意：Claude Desktop 不支持“采样”。这会带来一些限制。

子运行手册和可重复使用的执行块
用于管理运行手册的休息端点 + 前端。
能够编辑运行手册（带版本控制）
显示运行手册 X 的执行计划（试运行）
- 限制 MCP 服务器和工具
将之前的对话转换成运行手册
微调。
能够完善运行手册。如果执行成功，请将其保存为示例并交给 Claude。
定期执行
能够为运行 MCP 服务器提供环境（VM、docker）。

Available Tools

2 tools

create_runbookD

ParametersJSON Schema

Name	Required	Description	Default
`content`	Yes
`name`	Yes

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

Name	Required	Description	Default
`name`	Yes

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.

2 tool updatesv1.0.0Apr 2, 2025
- First observedcreate_runbook
- First observeddelete_runbook

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

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

GitHub Repository

Need Help?

Reddit Discussion

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

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

Related MCP Connectors

IFTTT MCP serverOAuth
com.ifttt
Automate 1,000+ services from any MCP-compatible AI agent: build Applets, run actions and queries.
App Automation
1
Computer-Use Agents API A
io.github.hcompai
Run and manage H Company's Computer-Use Agents from any MCP client.
Agent Orchestration Autonomous Agents
9231
LeadFoxConnectOAuth
io.github.LeadFox-Shay
Marketo MCP server for AI. 130 tools to operate Marketo from Claude, Cursor, or ChatGPT.
Marketing CRM
2
agentdocsOAuth
io.github.dancourse
An agent-first office suite Claude & ChatGPT read and write over one MCP URL.
Workplace & Productivity Documentation Access
2

Related MCP Servers

my-mcp-server
Code Execution Developer Tools
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.
Updated a year ago (2025-06-03 06:36 UTC)
47
-
MCP Server Generator
Developer Tools
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.
Updated a year ago (2025-06-12 13:54 UTC)
11
-
Expose
Developer Tools
deadcodedump
A
license
Not graded
quality
C
maintenance
Easily build MCP tools for Claude desktop app.
Updated a year ago (2025-03-22 14:42 UTC)
132
21
MIT
my-first-mcp
Code Execution Developer Tools
imranshareefshaik
A
license
Not graded
quality
D
maintenance
A local MCP server that connects Claude Desktop to execute custom local code, such as generating custom greetings.
Updated 5 months ago (2026-03-31 14:22 UTC)
7
ISC

Appeared in Searches

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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

Runbook MCP 服务器

如何使用

步骤 1. 使用 Claude Desktop 启动 MCP 服务器。

步骤 2.创建 Runbook

步骤 3. 运行 Runbook

可用于运行 Runbook 的示例 MCP 服务器

发展计划

可行性尚不明确的潜在工作项目

Available Tools

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

my-mcp-server

MCP Server Generator

Expose

my-first-mcp

Appeared in Searches

Latest Blog Posts

MCP directory API