Linux System MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| defer_loading | No | Set to "false" to disable defer loading and show all tools upfront. | true |
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 | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| linux_system_tool_searchA | [meta] Search for available linux_system tools by keyword. Use this when you need a specific capability but aren't sure which tool to call. Returns names, descriptions, and full schemas for matching tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| interactive_script_creation | Ask the user for a script idea, generate it, and ask for confirmation to run it. |
| open_workspace | Prompt the user for a directory path and open it in their unified desktop environment. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no ambiguity: the agent can uniquely identify the sole available tool.
A single tool trivially adheres to any naming convention; there is no inconsistency to penalize.
One tool is borderline thin for a 'Linux System' server; it suggests the server lacks meaningful functionality.
The server claims to manage a Linux system but provides only a self-search meta-tool with no actual system operations, leaving it severely incomplete.