CLI Exec offers a powerful CLI interface for command line execution, with timeout, ANSI code stripping, and error handli
Add new capabilities to Claude beyond text generation
Example: Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example: Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example: Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Time estimate: 15-60 minutes depending on server complexity
Prerequisites
Claude Context
Claude Context offers semantic code search and indexing with vector embeddings and AST-based code splitting. Natural lan
Shadcn io
MCP server connects Claude and AI coding tools to shadcn/ui components. Accurate TypeScript props and React component da
Chrome DevTools MCP
AI-driven control of live Chrome via Chrome DevTools: browser automation, debugging, performance analysis and network mo
Deepcon
Deepcon is an AI coding assistant server offering up-to-date package docs via semantic search for smarter, faster AI pow
Desktop Commander
Desktop Commander MCP unifies code management with advanced source control, git, and svn support—streamlining developmen
CLI Exec has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
We evaluated CLI Exec against two servers with overlapping tools; this profile had the clearer scope statement.
CLI Exec has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
CLI Exec reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We evaluated CLI Exec against two servers with overlapping tools; this profile had the clearer scope statement.
Useful MCP listing: CLI Exec is the kind of server we cite when onboarding engineers to host + tool permissions.
CLI Exec is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Useful MCP listing: CLI Exec is the kind of server we cite when onboarding engineers to host + tool permissions.
Strong directory entry: CLI Exec surfaces stars and publisher context so we could sanity-check maintenance before adopting.
CLI Exec is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
showing 1-10 of 64
Share your MCP server with the developer community
Select a client to integrate this server.
Claude Desktop configuration
{
"mcpServers": {
"mcp-cli-exec": {
"command": "npx",
"args": [
"-y",
"mcp-cli-exec"
]
}
}
}Executes shell commands with structured output including exit codes, stdout/stderr, and error handling. Provides both raw command execution and multi-command workflows in specific directories.
CLI Exec is a community-built MCP server published by jakenuts that provides AI assistants with tools and capabilities via the Model Context Protocol. CLI Exec offers a powerful CLI interface for command line execution, with timeout, ANSI code stripping, and error handli It is categorized under developer tools. This server exposes 2 tools that AI clients can invoke during conversations and coding sessions.
You can install CLI Exec in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
A powerful CLI command execution MCP server that enables running shell commands with structured output. This package focuses specifically on command execution functionality, differentiating it from other MCP CLI tools.
Execute a raw CLI command and return structured output
Execute one or more CLI commands in a specific working directory
Note: Due to execution context limitations, each command runs independently. Directory changes (cd) within commands do not affect subsequent commands. All commands execute in the initially specified working directory.
Commands return structured results including:
Simple command execution:
{
"command": "echo Hello World"
}
With timeout:
{
"command": "long-running-script.sh",
"timeout": 300000
}
Single command in specific directory:
{
"workingDirectory": "/path/to/project",
"commands": "npm install"
}
Multiple commands (all run in the same working directory):
{
"workingDirectory": "C:\project",
"commands": [
"dir /b",
"npm run build"
]
}
Optionally install from npm:
npm install -g mcp-cli-exec
# or with pnpm
pnpm add -g mcp-cli-exec
Or just use npx in your configuration
Add to %APPDATA%/Code - Insiders/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json:
{
"mcpServers": {
"mcp-cli-exec": {
"command": "npx",
"args": ["-y", "mcp-cli-exec"]
}
}
}
Add to the appropriate config file:
Windows: %APPDATA%/Claude/claude_desktop_config.json
MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"mcp-cli-exec": {
"command": "npx",
"args": ["-y", "mcp-cli-exec"]
}
}
}
If you encounter the ENOENT spawn npx issue on Windows, use this alternative configuration that specifies the full paths:
{
"mcpServers": {
"mcp-cli-exec": {
"command": "C:\Users\jim\AppData\Roaming\
vm\v22.1.0\
ode.exe",
"args": [
"C:\Users\jim\AppData\Roaming\
pm\
ode_modules\
pm\bin\
px-cli.js",
"-y",
"mcp-cli-exec"
]
}
}
}
Install dependencies:
pnpm install
Build the server:
pnpm run build
For development with auto-rebuild:
pnpm run watch
Since MCP servers communicate over stdio, debugging can be challenging. The MCP Inspector provides helpful debugging tools:
pnpm run inspector
This will provide a URL to access the inspector in your browser, where you can:
The server includes comprehensive error handling:
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.