nomad
Enables management of long-running remote tasks through tmux sessions, allowing task start, status, list, and kill operations.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@nomadpush code to devbox and run tests"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
nomad
nomad is a local MCP server for agentic remote development.
It helps an AI coding agent work with a remote machine while keeping the source
of truth on your local workstation: sync code with rsync, run short commands
over SSH, manage long-running jobs in remote tmux sessions, diagnose network
issues, and pull generated artifacts back into the local project.
Any MCP-enabled agent environment that can start a stdio server with a command and arguments can use nomad.
Features
Multi-target remote workspaces per local project.
Project-local
.nomad.jsonconfiguration with schema hints exposed through MCP.SSH preflight checks and read-only network diagnostics.
Incremental
rsyncpush with.gitignoreconversion and--deletedry-run protection.Remote artifact pull into project-owned local directories.
Short remote command execution with output truncation.
Long-running remote task management through
tmux.Optional persistent reverse SSH tunnel for sharing a local proxy with remote jobs.
Path guards, dangerous-command checks, and secret redaction for safer agent workflows.
Related MCP server: ssh-mcp
Requirements
Python 3.11+
sshrsynctmuxon remote machines when using long-running tasksKey-based SSH access to your remote targets
Installation
Run directly with uvx:
uvx nomad-mcpOr install it as an isolated global command with pipx:
pipx install nomad-mcpMCP Client Configuration
Use nomad as a stdio MCP server. The exact config file depends on your client.
Recommended no-install configuration:
{
"mcpServers": {
"nomad": {
"command": "uvx",
"args": ["nomad-mcp"]
}
}
}For TOML-based clients:
[mcp_servers.nomad]
command = "uvx"
args = ["nomad-mcp"]
startup_timeout_sec = 120If you installed with pipx, use the installed command instead:
{
"mcpServers": {
"nomad": {
"command": "nomad",
"args": []
}
}
}You can also print config snippets with:
nomad client-config
nomad client-config --runner nomad --format tomlQuick Start
Open an MCP-enabled agent in your local project directory.
Ask it to call
init_discover.Choose an SSH target and remote workspace path.
Ask it to save a
.nomad.jsonconfig withinit_save_config.Push code with
sync_push.Run short commands with
run_remote.Run long jobs with
task_start, then monitor them withtask_statusortask_list.Pull remote artifacts with
sync_pull.
Example .nomad.json
{
"project_name": "my_project",
"mode": "remote",
"default_target": "devbox",
"targets": {
"devbox": {
"description": "Primary remote development machine",
"ssh_host": "devbox",
"remote_path": "/data/my_project",
"local_subpath": null,
"auto_create_remote_path": true,
"network": {
"use_proxy_for_ssh": false,
"jump_host": null,
"reverse_tunnel": {
"enabled": false,
"proxy_scheme": "socks5"
}
},
"sync": {
"respect_gitignore": true,
"extra_excludes": []
},
"runtime": {
"interpreter": null,
"extra_env": {}
},
"limits": {
"command_timeout_seconds": 60,
"max_output_lines": 200,
"max_output_bytes": 10240
}
}
}
}run_remote uses limits.command_timeout_seconds. For downloads, builds,
training, fuzzing, and other slow work, prefer task_start so the job runs in a
remote tmux session and can be checked later.
Tools
init_discover: inspect the local workspace, SSH aliases, and proxy settings.init_verify_and_probe: verify SSH reachability and probe remote hardware/runtimes.init_save_config: validate and save.nomad.json.init_probe_target: refresh hardware/runtime information for a target.sync_push: push local code to the remote workspace.sync_pull: pull a remote file or directory into localremote_artifacts/.run_remote: run a short command in the remote workspace.task_start: start a long-running tmux task.task_status: inspect one task and return a log tail.task_list: list project-owned tasks across targets.task_kill: stop a task without deleting its logs.net_diagnose: run read-only SSH/network diagnostics.tunnel_start,tunnel_status,tunnel_stop: manage persistent reverse tunnels.
Safety Notes
nomad can execute commands over SSH and synchronize files with rsync. Use it
only with trusted local projects and trusted remote machines.
The server includes guardrails such as local/remote path checks, dangerous-command
blocking, .nomad.json sync exclusion, secret redaction, output truncation, and
rsync --delete dry-run protection. These guardrails reduce risk, but they do not
turn an untrusted agent or remote machine into a trusted one.
Development
python -m pip install -e .[dev]
nomad --version
nomad doctor
python -m pytest
python -m compileall -q src testsLicense
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Ad3n1ne/Nomad-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server