modelcontextprotocol / modelcontextprotocol/inspector
CLI has no shell completion (bash/zsh/fish)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10.9k
- Forks
- 1.5k
- Avg merge
- 6h 17m
- Merged PRs (30d)
- 151
Description
Which client?
CLI
The problem
mcp-inspector --cli has a fair number of subcommands and flags (tools/resources/prompts/servers, plus method-specific options), but there's no generated shell-completion script. Every invocation currently has to be typed from memory or looked up via --help, which slows down interactive CLI use noticeably compared to other Node-based CLIs that ship completions.
Solution you have in mind (optional)
Wire up completion generation via the CLI framework already in use (most Node CLI toolkits ship a completion generator) and document mcp-inspector --cli completion bash > ... in the CLI README.
Alternatives or workarounds you have tried
No response
Already built it locally?
No response
Before you submit
- I searched existing issues and this is not a duplicate.
- This is a request for the Inspector itself, not for the MCP specification or an SDK.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the mcp-inspector --cli entry point and inspect the CLI framework already in use for completion-generation support. Add bash, zsh, and fish completion generation, document mcp-inspector --cli completion bash > ... in the CLI README, and verify that completions cover the listed subcommands and flags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- cli, documentation
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100