Systemdox Runbooks

io.github.pugliesewebPublished by GitHub account pugliesewebv0.1.9Updated Oct 30, 2026

Your runbooks as agent tools: scripts from runbooks.json served as typed, allowlisted MCP tools.

VerifiedSTDIODesktop onlyCloud & Infrastructure Developer Tools

Server details

Identifier: io.github.puglieseweb/systemdox-runbooks
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account puglieseweb for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.puglieseweb%2Fsystemdox-runbooks.svg)](https://sourceweft.com/mcp/io.github.puglieseweb%2Fsystemdox-runbooks?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Turns scripts listed in a runbooks.json manifest into typed, allowlisted MCP tools that an assistant can call on the local machine.

What you can do: Expose each script defined in a runbooks.json manifest as a typed MCP tool.
Let the assistant invoke those allowlisted runbook scripts as tools.
Report the command a tool would run instead of executing it when dry-run mode is enabled.
When to use it: Useful when you already keep operational procedures as scripts and want an assistant to run them through a controlled, allowlisted set of tools rather than free-form shell access.
Requirements: Runs as a local stdio process from the npm package @systemdox/runbook-mcp, so Node.js is needed. A runbooks.json manifest must be supplied, either via the RUNBOOK_MCP_MANIFEST environment variable or the --manifest argument; it defaults to ./runbooks.json. Desktop only.

Before you install

The tools execute scripts from your manifest on the local machine, so only include commands you trust and review what each runbook does. Set RUNBOOK_MCP_DRY_RUN to 1 to preview commands before allowing real execution.

Installation

In SourceWeft

Open Systemdox Runbooks in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not start.

Version history

v0.1.9LatestOct 29, 2026
v0.1.5Oct 9, 2026
v0.1.3Sep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.