I built a CLI that tells you which MCP servers your repo actually needs

Description and use

The stackhint CLI automatically identifies and safely installs the necessary MCP servers, eliminating redundant dependencies and outdated configurations.

Problem

Developers struggle to identify which MCP servers are actually needed for their repository, often installing unnecessary or deprecated servers.

Outcome

stackhint automates the identification and safe installation of relevant MCP servers, reducing manual effort and preventing the use of deprecated or insecure servers.

Workflow

• 1. Run stackhint recommend with a task description to analyze the repo and receive recommendations.
• 2. Review the recommendations, which include relevance score, confidence, and justification.
• 3. Use stackhint install <server> to add a server, which prints a plan, writes atomically, and backs up the original file.
• 4. Optionally run stackhint try <server> to test without installing.
• 5. Use stackhint dismiss <server> to postpone a recommendation.
• 6. Run stackhint check to identify and replace deprecated or archived servers in the config.
• 7. Use stackhint rollback <id> to revert changes if needed.

Evidence

Every week someone posts another "top 10 MCP servers for Claude Code" list. I kept installing things from those lists, forgetting what I had, and once I noticed a project of mine was still running @modelcontextprotocol/server-postgres.

Source

It looks at a repository, checks what is already configured in Claude Code and Codex, and suggests the MCP servers, plugins, skills and CLIs that fit.

Source

It runs locally, has no dependencies and sends nothing anywhere.

Source

The analyzer reads the files that usually give a stack away: *.csproj, package.json, pyproject.toml, go.mod, compose files, Kubernetes and Terraform files, CI configs, .http files, the key names in .env.example, and links in the README.

Source

The ranking is a plain formula: relevance from the evidence, times value, minus setup cost and risk.

Source

stackhint install prints a plan first: where it will write, the diff, what the server can access, which environment variables it needs (by name only) and how to undo it.

Source