Skip to main content
Glama
enesjakozh
dillip285

MCP Terminal Server

by dillip285
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

MCP Terminal Server

A secure command-line interface server for the Model Context Protocol (MCP) that enables AI models to interact with your terminal while maintaining security and control.

Features

  • 🔒 Secure command execution with configurable permissions

  • 📁 File system operations within allowed paths

  • 🌍 Environment variable management

  • 💻 Cross-platform support (Windows, macOS, Linux)

  • 🔌 Remote system connections support via command execution

Related MCP server: Shell MCP Server

Usage with Claude Desktop

Add the server configuration to your Claude Desktop config file:

{
  "mcpServers": {
    "terminal": {
      "command": "npx",
      "args": [
        "@dillip285/mcp-terminal",
        "--allowed-paths",
        "/path/to/allowed/directory"
      ]
    }
  }
}

Restart Claude Desktop to apply the changes. You can now use the terminal capabilities through Claude with secure file access and command execution.

Available Tools

  • execute_command: Run terminal commands securely (including SSH and remote commands)

Security

  • All operations are restricted to specified allowed paths

  • Commands are validated and sanitized before execution

  • Environment variables are carefully managed

  • Proper error handling for security-related issues

Development

# Clone the repository
git clone https://github.com/dillip285/mcp-terminal.git

# Install dependencies
npm install

# Configure npm authentication
cp .npmrc.example .npmrc
# Edit .npmrc and add your NPM_TOKEN

# Run tests
npm test

# Build the project
npm run build

Publishing

To publish the package:

  1. Copy .npmrc.example to .npmrc

  2. Add your npm authentication token to .npmrc

  3. Run npm publish --access public

Note: Never commit your .npmrc file with the authentication token. It is already added to .gitignore.

Contributing

  1. Fork the repository

  2. Create your feature branch (git checkout -b feature/amazing-feature)

  3. Commit your changes (git commit -m 'feat: Add amazing feature')

  4. Push to the branch (git push origin feature/amazing-feature)

  5. Open a Pull Request

License

MIT License - see the LICENSE file for details.

Related Projects

Support

For bug reports and feature requests, please open an issue.

Available Tools

1 tool
execute_commandC

Execute a command in the local system

ParametersJSON Schema
NameRequiredDescriptionDefault
argsNoCommand arguments
commandYesCommand to execute
cwdNoWorking directory for command execution

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. While 'execute a command' implies a potentially powerful/mutating operation, it doesn't disclose critical behavioral traits like security implications, permission requirements, side effects, error handling, or output format. This leaves significant gaps for an AI agent to understand the tool's behavior.

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 extremely concise - a single sentence that directly states the tool's purpose without any unnecessary words. It's perfectly front-loaded with the essential information.

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?

For a tool that executes system commands (a potentially dangerous operation with no output schema), the description is severely lacking. It doesn't address security implications, permission requirements, typical use cases, error handling, or what kind of output/result to expect. The absence of annotations exacerbates these gaps.

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?

The schema description coverage is 100%, meaning all parameters are documented in the schema itself. The description doesn't add any meaningful parameter semantics beyond what's already in the schema (command, args, cwd). This meets the baseline expectation when schema coverage is complete.

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 action ('execute') and target ('a command in the local system'), providing a specific verb+resource combination. However, since there are no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, preventing a perfect score of 5.

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, nor does it mention any prerequisites, constraints, or typical use cases. It simply states what the tool does without contextual usage information.

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

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'execute_command' has a clear and distinct purpose that cannot be confused with any other tool in this set.

Naming Consistency5/5

The single tool name 'execute_command' follows a verb_noun pattern, and with only one tool, the naming is inherently consistent. There are no other tools to compare against, so no inconsistencies can arise.

Tool Count2/5

A single tool for a terminal server feels too minimal for the apparent scope. While it covers basic command execution, typical terminal operations might include listing files, navigating directories, or managing processes, suggesting a gap in functionality.

Completeness2/5

The tool surface is severely incomplete for a terminal server domain. It only allows command execution, missing essential operations like file browsing, process management, or environment inspection, which are core to terminal workflows and will likely cause agent failures.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • MCP Command Server

    Andrew-Beniash
    F
    license
    Not graded
    quality
    D
    maintenance
    A secure server that allows LLM applications like Claude to execute whitelisted system commands with user confirmation and comprehensive security features.

  • Shell MCP Server

    blazickjp
    A
    license
    B
    quality
    F
    maintenance
    A secure server that enables AI applications to execute shell commands in specified directories, supporting multiple shell types (bash, sh, cmd, powershell) with built-in security features like directory isolation and timeout control.
    1
    21
    Apache 2.0

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dillip285/mcp-terminal'

If you have feedback or need assistance with the MCP directory API, please join our Discord server