linux mcp server for Grok

io.github.rhel-lightspeed/linux-mcp-server

MCP server for read-only Linux system administration, diagnostics, and troubleshooting

client:Grok transport:stdio runtime:pypi

Install linux mcp server in Grok

.mcp.json (in your project root)

LINUX_MCP_USER

LINUX_MCP_SSH_KEY_PATH

LINUX_MCP_KEY_PASSPHRASE

LINUX_MCP_SEARCH_FOR_SSH_KEY

LINUX_MCP_COMMAND_TIMEOUT

LINUX_MCP_VERIFY_HOST_KEYS

LINUX_MCP_KNOWN_HOSTS_PATH

LINUX_MCP_ALLOWED_LOG_PATHS

LINUX_MCP_LOG_DIR

LINUX_MCP_LOG_LEVEL

LINUX_MCP_LOG_RETENTION_DAYS

Held in this page only — never stored, logged, or sent anywhere but back to your screen.

{
  "mcpServers": {
    "linux-mcp-server": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "linux-mcp-server"
      ],
      "env": {
        "LINUX_MCP_USER": "<LINUX_MCP_USER>",
        "LINUX_MCP_SSH_KEY_PATH": "<LINUX_MCP_SSH_KEY_PATH>",
        "LINUX_MCP_KEY_PASSPHRASE": "<LINUX_MCP_KEY_PASSPHRASE>",
        "LINUX_MCP_SEARCH_FOR_SSH_KEY": "<LINUX_MCP_SEARCH_FOR_SSH_KEY>",
        "LINUX_MCP_COMMAND_TIMEOUT": "<LINUX_MCP_COMMAND_TIMEOUT>",
        "LINUX_MCP_VERIFY_HOST_KEYS": "<LINUX_MCP_VERIFY_HOST_KEYS>",
        "LINUX_MCP_KNOWN_HOSTS_PATH": "<LINUX_MCP_KNOWN_HOSTS_PATH>",
        "LINUX_MCP_ALLOWED_LOG_PATHS": "<LINUX_MCP_ALLOWED_LOG_PATHS>",
        "LINUX_MCP_LOG_DIR": "<LINUX_MCP_LOG_DIR>",
        "LINUX_MCP_LOG_LEVEL": "<LINUX_MCP_LOG_LEVEL>",
        "LINUX_MCP_LOG_RETENTION_DAYS": "<LINUX_MCP_LOG_RETENTION_DAYS>"
      }
    }
  }
}

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

linux mcp server in other clients

linux mcp server MCP server