Skip to main content
Glama
enesjakozh
mkusaka

MCP Shell Server

by mkusaka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

MCP シェル サーバー

モデルコンテキストプロトコル（MCP）を使用してシェルコマンドを実行するサーバー。AIエージェントが安全にシェルコマンドを実行できるようにするブリッジとして機能します。

特徴

  • シェルコマンドを実行する（単一行および複数行のサポート）

  • さまざまなシェル (bash、zsh、fish、powershell、cmd など) のサポート

  • 詳細なエラー処理とログ記録

  • MCP Inspector対応

Related MCP server: Command Executor MCP Server

インストール

npmから（ユーザーとして）

# Using npm
npm install -g @mkusaka/mcp-shell-server

# Using yarn
yarn global add @mkusaka/mcp-shell-server

# Using pnpm
pnpm add -g @mkusaka/mcp-shell-server

ソースから（開発用）

# Clone the repository
git clone https://github.com/mkusaka/mcp-shell-server.git
cd mcp-shell-server

# Install dependencies
pnpm install

# Build the project
pnpm build

MCP構成

カーソルの設定

カーソル構成ファイル ( ~/.cursor/config.json ) に次のコードを追加します。

{
  "mcpServers": {
    "shell": {
      "command": "npx",
      "args": ["-y", "@mkusaka/mcp-shell-server"]
    }
  }
}

クライン統合

Clineは、Claude AIでMCPサーバーを利用できるようにするVS Code拡張機能です。ClineでMCPシェルサーバーを設定するには、以下の手順に従います。

  1. Cline MCP 設定ファイルを開きます。

    • macOS: ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

    • Windows: %APPDATA%/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

    • Linux: ~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

  2. シェル サーバーの MCP 構成を追加します。

    {
  "mcpServers": {
    "shell": {
      "command": "npx",
      "args": ["-y", "@mkusaka/mcp-shell-server"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

    あるいは、ローカルにインストールされたパッケージを使用する場合は、次のようにします。

    {
  "mcpServers": {
    "shell": {
      "command": "node",
      "args": ["/path/to/mcp-shell-server/dist/index.js"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

ルール設定

AI アシスタントのルールまたはプロンプトに次の内容を追加します。

You have MCP Shell tools at your disposal. Follow these rules regarding Shell tool usage:
1. ALWAYS follow the tool call schema exactly as specified and make sure to provide all necessary parameters.
2. **NEVER refer to tool names when speaking to me.** For example, instead of saying 'I need to use the shell_exec tool to run this command', just say 'I'll run that command for you'.
3. Only use Shell tools when they are necessary. If my task is general or you already know the answer, just respond without calling tools.
4. When I ask you to execute shell commands, use the appropriate tool to:
   - Run single-line commands
   - Run multi-line commands (using heredoc syntax when appropriate)
   - Execute file operations, git commands, or system utilities
   - Provide system information when relevant
5. Always be careful with shell commands that might modify the system, and explain what the command will do before executing it.
6. If a shell command produces an error, explain what went wrong in simple terms and suggest ways to fix it.

使用法

直接実行

node dist/index.js
# or as an executable
./dist/index.js

開発モード

pnpm dev

MCP Inspectorによるテスト

pnpm inspect

コマンドライン引数

-s, --shell <shell>  Specify the path to the shell to use
-w, --working-dir <directory>  Specify the working directory for command execution
-h, --help           Display help message
-V, --version        Display version information

ツールリファレンス

シェル実行

指定されたシェルでコマンドを実行します。

パラメータ:

  • command （文字列、必須）: 実行するシェルコマンド

  • workingDir (文字列、オプション): コマンドを実行する作業ディレクトリ。$HOME の下にある必要があります。

リソースリファレンス

サーバーは、リソースとして次のシステム情報を提供します。

ホスト名

システムのホスト名を返します。

URI: hostname://

プラットフォーム

オペレーティング システム プラットフォームを返します。

URI: platform://

シェル

サーバーで使用されているシェル パスを返します。

URI: shell://

ユーザー名

現在のユーザー名を返します。

URI: username://

システム情報

以下の情報を含む包括的なシステム情報を JSON 形式で返します。

  • ホスト名

  • プラットフォーム

  • シェル

  • ユーザー名

  • CPU数

  • 合計メモリ

  • 空きメモリ

  • システム稼働時間

使用例

基本的なコマンド実行

{
  "name": "shell_exec",
  "parameters": {
    "command": "echo Hello, World!"
  }
}

複数行コマンド（ヒアドキュメント）の実行

{
  "name": "shell_exec",
  "parameters": {
    "command": "cat << EOF | grep 'example'\nThis is an example text.\nAnother line without the keyword.\nEOF"
  }
}

発達

プロジェクト構造

src/
├── index.ts                # Main entry point
└── shell-server/
    ├── index.ts            # Shell server implementation
    └── lib/
        └── logger.ts       # Logging configuration

ログ記録

ログはmcp-shell.logファイルに書き込まれます。

ライセンス

マサチューセッツ工科大学

Available Tools

1 tool
shell_execC

Executes commands in the specified shell with detailed error handling and output capture

ParametersJSON Schema
NameRequiredDescriptionDefault
commandYesThe shell command to execute in the configured shell environment
workingDirNoOptional working directory to execute the command in (must be under $HOME for security)

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'detailed error handling and output capture' which adds some context beyond basic execution, but fails to address critical aspects like security implications, permission requirements, rate limits, or what happens when commands fail. For a shell execution tool with zero annotation coverage, this leaves significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose ('Executes commands in the specified shell') and adds value with secondary capabilities ('with detailed error handling and output capture'). Every word earns its place with zero waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of shell execution (security risks, variable outputs) and the absence of both annotations and an output schema, the description is insufficient. It doesn't explain return values, error formats, or security constraints beyond the schema's workingDir note. For a potentially dangerous tool with no structured safety indicators, more descriptive context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema (e.g., no examples of command syntax, working directory constraints beyond security). The baseline score of 3 reflects adequate schema coverage without description enhancement.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Executes commands in the specified shell' with additional capabilities for 'detailed error handling and output capture'. It uses specific verbs ('executes', 'capture') and identifies the resource ('shell commands'). However, there are no sibling tools mentioned, so differentiation from alternatives cannot be evaluated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or security considerations. It mentions 'detailed error handling and output capture' which implies some context, but offers no explicit when/when-not instructions or named alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedshell_exec
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'shell_exec' follows a clear verb_noun pattern.

Tool Count2/5

A single tool is generally too few for a server's purpose, as it limits functionality and may indicate an incomplete surface. However, for a simple shell execution server, it could be minimally viable but lacks breadth.

Completeness2/5

The tool provides basic shell command execution, but there are obvious gaps such as no tools for listing available commands, managing shell sessions, or handling file operations, making the surface severely incomplete for typical shell-related tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches