Linux MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINUX_MCP_COMPOSITOR_KEY | No | Compositor auth key (optional but recommended) |
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| file_readB | Read contents of a file |
| file_listC | List directory contents |
| app_launchC | Launch a desktop application by name |
| file_writeC | Write content to a file |
| clipboard_readB | Read current clipboard contents |
| notification_sendC | Send a desktop notification |
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 6 tools
Each tool has a clearly distinct purpose with no overlap: launching apps, reading clipboard, listing files, reading files, writing files, and sending notifications. An agent can easily distinguish between these functions without confusion.
All tool names follow a consistent snake_case pattern with clear verb_noun structure (e.g., app_launch, file_read, notification_send). There are no deviations in naming conventions across the set.
With 6 tools, this server is well-scoped for Linux desktop automation, covering key operations like file management, app launching, clipboard access, and notifications. Each tool earns its place without being excessive or insufficient.
The toolset covers core Linux desktop workflows effectively, including file operations, app interaction, and notifications. A minor gap exists in file management (e.g., no delete or move operations), but agents can work around this with the provided tools.