Cross-platform FastMCP server for authenticated remote Linux/macOS host administration
A cross-platform Model Context Protocol server for administering a Linux or macOS host through MCP clients such as ChatGPT and Claude.
It uses FastMCP Streamable HTTP transport, Auth0 OAuth, bounded file tools, output limits and command timeouts.
[!CAUTION] This project exposes arbitrary shell execution. Authentication decides who may use it; it does not make commands harmless. Read SECURITY.md before deploying it.
MCP_WORKSPACE_DIR| Tool | Parameters | Purpose |
|---|---|---|
run_command | command: str, timeout: int | Runs an arbitrary shell command with the workspace as its working directory |
read_file | path: str | Reads a text file inside the workspace |
write_file | path: str, content: str | Writes UTF-8 text inside the workspace |
list_dir | path: str = "." | Lists a directory inside the workspace |
system_metrics | none | Reports disk, memory and top-process information |
The workspace boundary applies to the file tools. It does not sandbox run_command; commands retain all permissions of the service's OS user.
pip install universal-host-manager-mcp
Without polluting a project environment:
uvx universal-host-manager-mcp
git clone https://github.com/Abktya/universal-host-manager-mcp.git
cd universal-host-manager-mcp
python3 -m venv .venv
source .venv/bin/activate
pip install -e .
cp .env.example .env
Create a .env file (copy .env.example if you installed from source) with an explicitly restricted workspace:
HOST=127.0.0.1
PORT=8765
MCP_BASE_URL=https://mcp.example.com
MCP_WORKSPACE_DIR=/home/youruser/workspace
AUTH0_DOMAIN=your-tenant.eu.auth0.com
AUTH0_CLIENT_ID=replace_me
AUTH0_CLIENT_SECRET=replace_me
AUTH0_AUDIENCE=https://mcp.example.com/
Never commit .env.
This project uses FastMCP's Auth0Provider fixed-client OAuth integration.
https://mcp.example.com/..env.FastMCP also supports an Auth0 MCP-native/DCR path through Auth0MCPProvider. This repository currently uses the manually managed, fixed-client Auth0Provider path.
universal-host-manager-mcp
(Running from a source checkout with the .venv activated works the same way — the console script is installed by pip install -e ..)
With the default port, the Streamable HTTP endpoint is:
http://127.0.0.1:8765/mcp
For an intentional local-only test without Auth0:
ALLOW_INSECURE_NO_AUTH=true universal-host-manager-mcp
Do not use insecure mode on a publicly reachable endpoint.
Install cloudflared, authenticate it and create a named tunnel:
cloudflared tunnel login
cloudflared tunnel create universal-host-manager-mcp
cloudflared tunnel route dns universal-host-manager-mcp mcp.example.com
Create ~/.cloudflared/config.yml:
tunnel: YOUR_TUNNEL_ID
credentials-file: /home/youruser/.cloudflared/YOUR_TUNNEL_ID.json
ingress:
- hostname: mcp.example.com
service: http://127.0.0.1:8765
- service: http_status:404
Validate and run it:
cloudflared tunnel ingress validate
cloudflared tunnel run universal-host-manager-mcp
Your remote MCP URL will be:
https://mcp.example.com/mcp
Set MCP_BASE_URL=https://mcp.example.com; do not include /mcp in MCP_BASE_URL.
These steps deploy the server on an EC2 instance and expose it safely to remote MCP clients.
apt; on Amazon Linux 2023 use sudo dnf install -y python3-pip instead)t3.micro/t3.small is enough for typical management workloadsSSH into the instance, then install from PyPI:
sudo apt update && sudo apt install -y python3-pip python3-venv
python3 -m venv ~/uhm-venv
source ~/uhm-venv/bin/activate
pip install universal-host-manager-mcp
mkdir -p ~/workspace
cat > ~/.env << 'EOF'
HOST=127.0.0.1
PORT=8765
MCP_BASE_URL=https://mcp.example.com
MCP_WORKSPACE_DIR=/home/ubuntu/workspace
AUTH0_DOMAIN=your-tenant.eu.auth0.com
AUTH0_CLIENT_ID=replace_me
AUTH0_CLIENT_SECRET=replace_me
AUTH0_AUDIENCE=https://mcp.example.com/
EOF
chmod 600 ~/.env
Keep HOST=127.0.0.1. The server should never listen directly on the instance's public interface — internet exposure is handled entirely by the tunnel or load balancer described below, not by opening the instance's own port.
Auth0 OAuth requires HTTPS. Pick one option:
Option A — Cloudflare Tunnel (recommended, no inbound port needed)
Run the steps from the Cloudflare Tunnel section above, from the EC2 instance. Because the tunnel is an outbound-only connection, you don't need to open any inbound port beyond SSH, don't need an Elastic IP, and the instance can even sit in a private subnet behind a NAT gateway.
Option B — Application Load Balancer with an ACM certificate
PORTPORT only from the ALB's security group, never from 0.0.0.0/0MCP_BASE_URL to that hostnameReuse the included unit (see Background service below):
sudo cp examples/mcp-manager.service /etc/systemd/system/
# edit User=, WorkingDirectory=, EnvironmentFile= and ExecStart= to point at
# ~/uhm-venv/bin/universal-host-manager-mcp and ~/.env
sudo systemctl daemon-reload
sudo systemctl enable --now mcp-manager
sudo systemctl status mcp-manager --no-pager
Not required for either networking option. The Cloudflare Tunnel connects outbound regardless of the instance's address, and an ALB registers targets by instance ID or private IP, so it doesn't need one either. Only add an Elastic IP if something else in your setup depends on a fixed public IP for this instance.
Add the public Streamable HTTP URL to the client's MCP/connector configuration:
https://mcp.example.com/mcp
Complete the Auth0 sign-in when the client opens the authorization flow. The exact settings screens and supported connector options can change, so follow the current client documentation rather than using legacy SSE instructions.
Multiple clients can connect to the same running HTTP server. Each client authenticates independently; no separate server process or port is required.
Copy and edit the included unit:
sudo cp examples/mcp-manager.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable --now mcp-manager
sudo systemctl status mcp-manager --no-pager
The example uses systemd hardening directives. Adjust ReadWritePaths, ProtectHome, the user, paths and permissions to match the resources the MCP server genuinely needs.
Edit paths in examples/com.user.mcpmanager.plist, then:
cp examples/com.user.mcpmanager.plist ~/Library/LaunchAgents/
launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/com.user.mcpmanager.plist
launchctl kickstart -k gui/$(id -u)/com.user.mcpmanager
| Variable | Default | Description |
|---|---|---|
HOST | 127.0.0.1 | Listen address |
PORT | 8765 | Listen port |
MCP_BASE_URL | local URL | Public OAuth base URL, without /mcp |
MCP_WORKSPACE_DIR | user home | Boundary for file tools and command working directory |
MAX_OUTPUT_CHARS | 64000 | Maximum returned tool-output characters |
DEFAULT_CMD_TIMEOUT | 300 | Default command timeout in seconds |
MAX_CMD_TIMEOUT | 1800 | Maximum accepted command timeout |
MAX_READ_BYTES | 5000000 | Maximum file size read by read_file |
MAX_WRITE_BYTES | 5000000 | Maximum content size written by write_file |
LOG_LEVEL | INFO | Python log level |
ALLOW_INSECURE_NO_AUTH | false | Explicit local-development authentication bypass |
Clone with Git:
git clone https://github.com/Abktya/universal-host-manager-mcp.git
Or use Code → Download ZIP on GitHub.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
uvx universal-host-manager-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-abktya-universal-host-manager-mcp": {
"command": "uvx",
"args": [
"universal-host-manager-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceio.github.Abktya/universal-host-manager-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.