nomad
A local MCP server for agentic remote development that enables code sync via rsync, SSH command execution, and long-running task management in remote tmux sessions.
README
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.
Requirements
- Python 3.11+
sshrsynctmuxon remote machines when using long-running tasks- Key-based SSH access to your remote targets
Installation
Run directly with uvx:
uvx nomad-mcp
Or install it as an isolated global command with pipx:
pipx install nomad-mcp
MCP 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 = 120
If 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 toml
Quick 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 tests
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。