zoxide-doctor MCP server
Read-only local zoxide diagnostics for MCP clients.
0 stars52 downloads/wk
Reviews
Write oneNobody has reviewed zoxide-doctor yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
zoxide-doctor tools (1, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
diagnose_zoxidewrite actionRun read-only local diagnostics for zoxide PATH availability, shell initialization, and optional fzf support. Shell profile content is read only when scan_config is true.
Public scan report
scanner v0.1.10 · 2026-11-04 · same rubric, same numbers if you re-run it
- Code scan4 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 87 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How zoxide-doctor compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,243 servers
- Tools
- 1
- the typical server has 7
- Tools that change things
- 100%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 52
- more than 42% of 12,306 servers with a package
What its tools let an agent do: 1 change
Install zoxide-doctor in Claude Code, Cursor or VS Code
Runs npx -y @agoes/zoxide-doctor-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add zoxide-doctor -- npx -y @agoes/zoxide-doctor-mcp
What the publisher says
From the zoxide-doctor repository's README, as published. We do not edit it. Read it on GitHub
zoxide-doctor MCP server
@agoes/zoxide-doctor-mcp gives MCP clients one local, read-only tool for diagnosing zoxide installation and shell setup. It wraps the published zoxide-doctor diagnostic core; it does not install zoxide or modify shell configuration files.
This is an independent community integration. It is not affiliated with or endorsed by the official zoxide project.
What it does
- Checks whether zoxide and optional fzf are on PATH.
- Checks that zoxide init produces shell initialization code.
- Returns a machine-readable JSON report, including the matching zoxide.org setup and troubleshooting guides.
- Reads conventional shell profile paths only when the MCP caller sets scan_config: true.
Install for an MCP client
Use an MCP client configuration that starts the local stdio server with npx:
{
"mcpServers": {
"zoxide-doctor": {
"command": "npx",
"args": ["-y", "@agoes/zoxide-doctor-mcp"]
}
}
}The server exposes one tool:
diagnose_zoxide({ shell?: "bash" | "zsh" | "fish" | "powershell" | "nushell" | "elvish" | "tcsh" | "xonsh" | "posix", scan_config?: boolean })scan_config is opt-in because it reads conventional shell-profile files. The tool never writes files or changes shell state.
Development
npm install
npm run lint
npm test
npm run validate:metadata
npm run pack:check
npm run smokeserver.json is kept version-locked to package.json and sets the MCP Registry websiteUrl to the zoxide-doctor guide.
License
MIT
Nothing above is checked by us. What we check is on the safety report.
zoxide-doctor: common questions
- Is zoxide-doctor MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the zoxide-doctor safety report
- How do I install zoxide-doctor?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does zoxide-doctor need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is zoxide-doctor maintained?
- The last commit was 88 days ago (2026-08-09). The latest release is v0.1.2.
- How does zoxide-doctor compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,243 servers); tools 1 (the typical server has 7); tools that change things 100% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.