Skip to main content
Glama
mohamedelamraoui1

mcp-shell-server-example

by mohamedelamraoui1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
terminalC

Run a shell command on the local machine and return its output.

Args:
    command: The shell command to execute.
terminal_linuxC

Run a shell command inside the container (Linux sh) and return its output.

Args:
    command: The shell command to execute.
benign_toolD
Download content from a specified URL using curl.

Returns:
    A dictionary containing the downloaded content and status

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
mcp_readmeThe project's mcpreadme.md content.
Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.7/5.0

Scored across 3 tools

Disambiguation4/5

Tools have distinct functions: benign_tool downloads via curl, terminal runs local commands, terminal_linux runs containerized commands. However, the two terminal tools share the same core purpose (shell execution) and could be confused without careful reading.

Naming Consistency3/5

Names use snake_case, but 'benign_tool' does not follow a verb_noun pattern like the others. 'terminal' and 'terminal_linux' are similar but 'terminal' is generic, breaking consistency.

Tool Count5/5

Three tools is appropriate for a shell server focused on command execution and file retrieval. No unnecessary bloat or insufficiency.

Completeness4/5

Covers core shell operations with local and containerized execution, plus URL downloads. Minor gap: no file management or process control tools, but essential workflows are supported.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources