Module install 

mushroomdb install / uninstall — wire the /mushroom skill and MCP server into Claude Code and Cursor.

Design notes

• No network: writes local config only; binary is already on disk.
• Idempotent: running install twice is a no-op (exit 0).
• Non-destructive: refuses to overwrite user files install didn’t create.
• Manifest-driven uninstall: tracks every file written; removes exactly what install created.

User-scope MCP config location (verified 2026-09-02 by live inspection)

Claude Code user-level MCP servers live in ~/.claude.json under the top-level "mcpServers" key. This was verified empirically on a live Claude Code install: ~/.claude/settings.json holds env/permissions/hooks but NO mcpServers key. Cursor uses ~/.cursor/mcp.json (same format as project-level .cursor/mcp.json).

Structs

InstallOpts

Options parsed from mushroomdb install [flags] or mushroomdb uninstall [flags].

Enums

BinaryLocation

How the MCP server entry (and the skill’s bootstrap commands) invoke mushroomdb.

Platform

Which assistant platform(s) to wire up.

Functions

classify_binary_location

Pure classifier behind detect_binary_location: decide whether the mushroomdb that PATH resolves to is the executable now running.

detect_binary_location

Decide how the MCP entry should invoke mushroomdb, from the real environment.

run_install

Install the /mushroom skill and MCP server entry for the resolved platforms.

run_install_with

Like run_install, but with the binary location supplied by the caller instead of detected from PATH / current_exe. Tests use this to stay deterministic; run_install is the real-environment wrapper.

run_uninstall

Uninstall: remove exactly what install wrote. Reads the manifest.