
Boot Doctor Mcp
io.github.pamela-0Published by GitHub account pamela-0v0.1.0Updated Oct 24, 2026
Deterministic PC no-boot/no-POST diagnostics: real beep-code tables, no LLM guessing.
Overview
A local MCP server that gives an assistant deterministic PC no-boot and no-POST troubleshooting steps and sourced BIOS beep-code lookups.
- What you can do
- Rank next troubleshooting steps for a PC that powers on but shows no display, based on symptoms and what has already been tried, following a power-stage, CMOS reset, minimal-config and swap-test sequence ordered by cost to rule out first. Look up a beep pattern such as short or long beep counts against sourced BIOS beep-code tables for AMI legacy, AMI Aptio and Award/Phoenix, kept separate because their codes differ. Return an honest no-match result when a pattern is not in the table, rather than a fabricated guess.
- When to use it
- Useful when helping someone troubleshoot a desktop that will not boot or show output and you want fixed, auditable rules instead of a model guessing at a failed component. Also handy for interpreting BIOS beep patterns during hardware triage.
- Requirements
- Runs locally as a Python package installed with pip; add it to the MCP client configuration or run it as a Python module. No accounts, API keys, environment variables or headers are declared. The README says beep-code data is fetched and cross-referenced live, so network access may be needed.
Installation
In SourceWeft
- Open Boot Doctor Mcp 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
boot-doctor-mcp
A real MCP server for PC no-boot / no-display / no-POST troubleshooting. No LLM guessing at hardware causes — a plain, deterministic rule engine plus real, sourced BIOS beep-code tables.
Why deterministic, not an LLM
Nobody wants a language model hallucinating "your GPU is dead" when it isn't. Hardware advice where being wrong costs real money and real time deserves a fixed, auditable rule set, not a plausible-sounding guess. Every answer this tool gives traces back to a real source or a fixed, testable rule — never an invented explanation.
Tools
diagnose_symptoms(powers_on, fans_spin=None, fans_stay_running=None, display_output=False, tried_cmos_reset=False, tried_minimal_config=False, tried_different_cable_or_monitor=False)
Real, ranked next troubleshooting steps, given what's already been tried — the same power-stage → CMOS reset → minimal-config-test → swap-test sequence a real technician runs, ordered by what's cheapest to rule out first. Not a diagnosis of the exact broken part; a real repair often still needs a swap test against known-good parts, and this tool says so explicitly rather than pretending symptom-matching alone can replace it.
lookup_beep_code(bios_type, pattern)
Looks up a beep pattern (e.g. "10 short", "1 long, 2 short", "continuous") against real, sourced BIOS beep-code tables.
bios_type is one of:
ami_legacy— classic AMIBIOSami_aptio— modern AMI Aptio (UEFI), kept separate on purpose: legacy AMIBIOS and Aptio use genuinely different codes for the same beep counts, a mistake common in beginner troubleshooting guides that merge them into one tableaward_phoenix— Award/Phoenix BIOS
Returns real information, not a fabricated guess, when the exact pattern isn't in the table — modern boards increasingly have no speaker at all and use debug LEDs instead, so "no match" is itself a real, honest result.
Sources
Beep-code data fetched and cross-referenced live (not from training-data memory) from IONOS and Thomas-Krenn. Real, stated limitation: OEMs (HP, Dell, ASUS, etc.) sometimes customize or extend these codes, and modern boards increasingly skip the speaker entirely in favor of debug LEDs — a documented pattern not matching here doesn't necessarily mean nothing is wrong.
Install
Add to your MCP client config (e.g. Claude Code):
Or run directly for local testing:
Skill
A SKILL.md ships inside this same package — not a separate download — and teaches Claude when and how to use these tools correctly (e.g. never guessing a BIOS type, never stating a broken component as fact from symptoms alone). Install it into your project:
Run it from the project root you want the skill active in — it writes to .claude/skills/boot-doctor-mcp/SKILL.md relative to your current directory.
Development
Source: README.md at commit 5faf129
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
50% 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
- License10 pts