mcp-linux-ops
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_commandB | 在 Linux 系统上执行 shell 命令 |
| read_fileC | 读取文件内容 |
| write_fileC | 写入文件内容 |
| list_directoryC | 列出目录内容 |
| create_directoryC | 创建目录 |
| delete_fileC | 删除文件或目录 |
| file_existsB | 检查文件或目录是否存在 |
| get_file_infoB | 获取文件或目录的详细信息 |
| copy_fileB | 复制文件或目录 |
| move_fileA | 移动或重命名文件或目录 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool maps to a distinct action (execute, read, write, list, create, delete, check, info, copy, move), with no overlap. Even though file and directory operations are combined in some tools, descriptions clarify that they handle both, eliminating ambiguity.
Most tools follow a consistent verb_noun pattern (e.g., read_file, create_directory, copy_file). The only exception is file_exists, which uses noun_verb, creating a minor inconsistency that prevents a perfect score.
10 tools is well within the ideal range for a Linux file operations server. Each tool covers a distinct operation with no redundancy, and the count feels appropriately scoped for the purpose.
The server covers the full lifecycle for files and directories: create, read, write, delete, list, copy, move, check existence, and get info, plus arbitrary command execution. This is a complete surface for the stated domain, with no obvious dead ends or missing critical operations.