Super Shell MCP Server

Created By
cfdudea year ago
Super Shell MCP
Overview

What is Super Shell MCP?

Super Shell MCP is a Model Context Protocol (MCP) server designed for executing shell commands across multiple platforms, including Windows, macOS, and Linux, with a focus on security and command management.

How to use Super Shell MCP?

To use Super Shell MCP, you can install it via NPX or manually clone the repository, install dependencies, and start the server. Configuration is done through JSON files for different platforms.

Key features of Super Shell MCP?

  • Executes shell commands on Windows, macOS, and Linux with automatic platform detection.
  • Supports multiple shells: cmd.exe, PowerShell, zsh, bash, and sh.
  • Command whitelisting with security levels: safe, requires approval, and forbidden.
  • Non-blocking approval workflow for potentially dangerous commands.
  • Comprehensive logging system and command management tools.

Use cases of Super Shell MCP?

  1. Securely executing shell commands in a multi-platform environment.
  2. Managing command execution with approval workflows for enhanced security.
  3. Logging and monitoring command usage for auditing purposes.

FAQ from Super Shell MCP?

  • Can Super Shell MCP run on all major operating systems?

Yes! It supports Windows, macOS, and Linux.

  • Is there a way to customize command permissions?

Yes! You can configure command whitelists and security levels based on your needs.

  • How does the logging system work?

The server logs all operations, including command executions and approval workflows, to a file for easy monitoring.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
cfdude
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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