Dynamic Shell Server

Created By
codeliona year ago
A Model Context Protocol (MCP) server that enables secure execution of shell commands with a dynamic approval system. This server allows running arbitrary commands while maintaining security through user approval and audit logging.
Overview

what is Dynamic Shell Server?

Dynamic Shell Server is a Model Context Protocol (MCP) server that enables secure execution of shell commands with a dynamic approval system, allowing users to run arbitrary commands while maintaining security through user approval and audit logging.

how to use Dynamic Shell Server?

To use the Dynamic Shell Server, clone the repository, set up a virtual environment, install dependencies, and run the server. Users can also integrate it with Claude Desktop for enhanced functionality.

key features of Dynamic Shell Server?

  • 🔐 Dynamic command approval system
  • 📝 Persistent storage of approved commands
  • 📊 Comprehensive audit logging
  • ⏱️ Command timeout protection
  • 🔄 Command revocation capability

use cases of Dynamic Shell Server?

  1. Securely executing shell commands in a controlled environment.
  2. Maintaining an audit trail of command executions for compliance.
  3. Allowing users to approve commands dynamically to enhance security.

FAQ from Dynamic Shell Server?

  • How does the command approval process work?

Users are prompted to approve commands the first time they are executed, with options to allow once, remember for future use, or deny execution.

  • Is there a way to revoke command approvals?

Yes! Users can revoke approval for previously approved commands at any time.

  • What security measures are in place?

The server requires user approval for first-time command execution, has persistent storage for approved commands, and includes comprehensive audit logging.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
codelion
Star
-
Language
-
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