Modern CLI MCP Server
Expose 104+ modern CLI utilities to your agent as JSON-friendly MCP tools instead of fragile shell one-liners.
Overview
io.github.NacoSolutions/modern-cli-mcp is a MCP server for the Build phase that exposes 104+ modern CLI tools to agents with JSON-first output.
What is this MCP server?
- 104+ CLI tools organized across 15 advertised feature categories
- AI-optimized JSON output by default for agent parsing
- Categories include filesystem, git, search, containers, Kubernetes, and data transforms
- Zero-config installation path documented via Nix
- .agentignore access control for scoped filesystem operations
- 104+ CLI tools across 15 categories per registry publisher features
- Documented tool families include data, diff, search, system, network, utilities, containers, and filesystem
What problem does it solve?
Agents struggle to run diverse shell tools reliably and parse unstructured terminal output during implementation work.
Who is it for?
Solo builders who want one MCP gateway to ripgrep, jq, container tooling, and sysutils while coding with an agent.
Skip if: Builders who only need a single CLI wrapper or who cannot install the underlying binaries on their machine.
What do I get? / Deliverables
After install, your agent gains MCP tools spanning search, git, containers, and data utilities with consistent JSON responses.
- Broad MCP tool surface over 104+ CLIs
- Structured JSON responses for agent consumption
- Filesystem and container operations behind access controls
Recommended MCP Servers
Journey fit
While building, agents need safe structured access to ripgrep, jq, containers, and git-adjacent CLIs—this server centralizes that behind MCP. Integrations subphase fits a bridge that turns host-installed binaries into agent-callable tools with consistent JSON output.
How it compares
Aggregated CLI bridge MCP, not a single-purpose database or browser automation server.
Common Questions / FAQ
Who is modern-cli-mcp for?
Developers using MCP agents who want broad terminal tooling—search, git, containers, data—in one JSON-oriented server.
When should I use modern-cli-mcp?
Use it during build work when your agent repeatedly needs structured output from modern CLIs instead of ad-hoc bash.
How do I add modern-cli-mcp to my agent?
Install via the published npm/Nix paths from NacoSolutions, ensure required CLI binaries exist on the host, then register the stdio MCP server in Claude Code or Cursor.