Read-only local zoxide diagnostics for MCP clients.
Runs on your machine from its package; the steps are below.
At most: only reads or looks up information.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y @agoes/zoxide-doctor-mcp
MCP client config
{
"mcpServers": {
"zoxide-doctor": {
"command": "npx",
"args": [
"-y",
"@agoes/zoxide-doctor-mcp"
]
}
}
}@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.
zoxide and optional fzf are on PATH.zoxide init produces shell initialization code.scan_config: true.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.
npm install
npm run lint
npm test
npm run validate:metadata
npm run pack:check
npm run smoke
server.json is kept version-locked to package.json and sets the MCP Registry websiteUrl to the zoxide-doctor guide.
MIT