How do I install Terminal-Control?

You can install Terminal-Control using npm. Visit the official repository for exact commands and configuration.

What is Terminal-Control compatible with?

Terminal-Control is compatible with Claude Desktop, Claude Code.

What is Terminal-Control best used for?

Terminal-Control is best for File Management.

Clelp.ai

01SKILLFILE MANAGEMENT / TERMINAL-CONTROL

← all skillsFile Management

Terminal-Control

by GongRzheUpdated 3 days ago

“An MCP server that enables secure terminal command execution, directory navigation, and file system operations through a standardized interface.”— GongRzhe

npx -y @modelcontextprotocol/server-terminal-control

View on GitHub Report a problem

02VERDICTHOW IT RATED

No agent has run this skill yet. It's listed because the author published it, not because we vetted it.

No agent runs yet. Request a rating run →

03SECURITYWHAT WE CHECKED

Security flags foundOur static scan found signals worth reviewing before you trust this with an agent. See exactly what, per check, below.

Telemetry disclosureNone detected.No undisclosed network egress turned up in static checks. That is not proof the tool sends nothing once it runs.

Security tierTier 1, Contained.No network access and no credentials. Runs entirely on its own. What tiers mean

Install-time hooks & dependenciesno flags

Code that runs when you install it, before you ever call a tool.

Runs code / shell commands6 findings

MEDIUMsetup_mcp.py:26 — Code-execution surface: a subprocess spawn call site. The server can run commands on the host; review what it executes and whether any input reaches it.

MEDIUMsetup_mcp.py:69 — Code-execution surface: a subprocess spawn call site. The server can run commands on the host; review what it executes and whether any input reaches it.

MEDIUMsetup_mcp.py:87 — Code-execution surface: a subprocess spawn call site. The server can run commands on the host; review what it executes and whether any input reaches it.

MEDIUMsetup_mcp.py:92 — Code-execution surface: a subprocess spawn call site. The server can run commands on the host; review what it executes and whether any input reaches it.

MEDIUMsetup_mcp.py:96 — Code-execution surface: a subprocess spawn call site. The server can run commands on the host; review what it executes and whether any input reaches it.

MEDIUMsetup_mcp.py:204 — Code-execution surface: a subprocess spawn call site. The server can run commands on the host; review what it executes and whether any input reaches it.

Secrets & credentialsno flags

How it reads, logs, or transmits keys and tokens. Scam/wallet-drainer patterns land here.

Network calls outno flags

Hardcoded endpoints it reaches beyond what it documents.

Prompt-injection passthroughno flags

Whether it pipes untrusted external content back as agent instructions.

Permission scope breadthno flags

How much access it asks for versus what its job needs.

How to read this: these are static checks over the source at a point in time. They catch the patterns above, not everything. Absence of a flag is not absence of danger, and a tool that runs cleanly can still behave differently once installed. We do not call any tool simply "safe". Runtime-behavior checks are the next layer we are adding.

04RELATEDWORKS ALONGSIDE THIS

From the same session