Linux Command MCP (Model Context Protocol)

Created By
xkiranja year ago
MCP server and client for running Linux commands
Overview

what is Linux Command MCP?

Linux Command MCP (Model Context Protocol) is a remote command execution system that allows users to securely and standardizedly execute Linux commands from a client to a server.

how to use Linux Command MCP?

To use Linux Command MCP, set up the server by configuring the claude_desktop_config.json file, start the server using PM2, and then use the client to execute commands.

key features of Linux Command MCP?

  • Secure remote execution of Linux commands
  • Standardized command execution through a client-server model
  • Support for various command types, including listing directories and checking system information

use cases of Linux Command MCP?

  1. Executing Linux commands remotely in a secure environment.
  2. Automating system checks and diagnostics.
  3. Providing a controlled interface for users to interact with Linux systems without direct access.

FAQ from Linux Command MCP?

  • Can I run interactive commands like sudo?

No, the Linux Command MCP server cannot execute interactive commands like sudo. You need to run such commands manually on the server.

  • What should I do if I encounter issues?

Check if PM2 is running, verify server logs, and ensure that both server and client builds are correct.

  • Is there a way to contribute to the project?

Yes! You can contribute by adding more command examples, enhancing documentation, or suggesting improvements.

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