stackhint
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NO_COLOR | No | Disable colored output when set. | |
| CODEX_HOME | No | Codex configuration directory, respected like the client does. | |
| STACKHINT_HOME | No | State folder for stackhint (defaults to ~/.stackhint). | |
| CLAUDE_CONFIG_DIR | No | Claude Code configuration directory, respected like the client does. | |
| STACKHINT_REGISTRY | No | Extra registry files, separated by your OS path delimiter. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| recommend_toolsA | Scan the project (locally, read-only) and list MCP servers, plugins, skills and CLIs that fit it and the current task, skipping ones already set up. Pass a short task description for task-specific advice. Never installs anything. |
| explain_toolA | Details for one registry entry: what it does, why it fits (or not), permissions, risks, setup, and the exact config it would add. |
| search_toolsC | Search the local curated registry by keyword (offline). |
| tooling_statusA | List MCP servers, plugins and skills configured for Claude Code and Codex, plus problems such as outdated servers or secrets written into config files. |
| plan_installA | Show exactly what installing a tool would change (diff, permissions, env vars). It does NOT apply anything. To install, ask the user to run the printed |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: recommendation, keyword search, per-entry explanation, environment status, and install preview. While search and recommend both surface tools, their inputs and outputs are distinct enough to avoid meaningful misselection.
Most names follow a verb_noun pattern in snake_case: recommend_tools, explain_tool, search_tools, plan_install. tooling_status is the one deviation, using a noun phrase rather than a verb, but it is still readable and consistent in casing.
Five tools is well-scoped for a local tooling advisor: search, recommend, explain, plan, and status each earn their place. The surface is neither thin nor bloated.
The set covers discovery, evaluation, install planning, and configuration status, which are the core workflows for an advisory MCP server. It intentionally omits applying installs or managing removal/update operations, which is a minor gap but consistent with its safety-focused design.