MCP CLI

Created By
gelisama year ago
a simple MCP server allowing VS Code to run a specific shell command without asking
Overview

what is MCP CLI?

MCP CLI is a Model Context Protocol server that allows AI assistants like GitHub Copilot to run specific shell commands without requiring user permission each time.

how to use MCP CLI?

To use MCP CLI, clone the repository, install it, and configure it in VS Code to add the MCP server as a tool. You can then use the command #mcp-cli in your prompts to instruct the AI to execute shell commands.

key features of MCP CLI?

  • Allows AI assistants to run shell commands without repeated permissions.
  • Supports a customizable list of allowed commands.
  • Integrates seamlessly with VS Code for enhanced productivity.

use cases of MCP CLI?

  1. Automating repetitive shell command executions in coding environments.
  2. Enhancing AI assistant capabilities by allowing them to perform tasks that require shell commands.
  3. Streamlining workflows for developers using VS Code.

FAQ from MCP CLI?

  • Can MCP CLI run any shell command?

Yes, as long as the command is added to the allowed list in the configuration.

  • Is MCP CLI free to use?

Yes! MCP CLI is open-source and free for everyone.

  • How do I modify the allowed commands?

You can modify the allowed commands in the .vscode/mcp.json configuration file.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gelisam
Star
2
Language
Haskell
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago