README.md
Unified mesh control layer for distributed infrastructure
OmniWire
Unified mesh control layer for distributed infrastructure 30-tool MCP server • SSH2 connection pooling • adaptive file transfers • cross-node config sync
OmniWire connects all your machines into a single control plane. It exposes 30 MCP tools that any AI agent (Claude Code, OpenCode, Cursor, etc.) can use to execute commands, transfer files, manage Docker containers, and sync configurations across your entire infrastructure — through one unified interface.
┌──────────────────────────────────────────────────────────────┐
│ AI Agent (MCP Client) │
│ Claude Code / OpenCode / Cursor │
└──────────────────────┬───────────────────────────────────────┘
│ MCP Protocol (stdio / SSE / REST)
▼
┌──────────────────────────────────────────────────────────────┐
│ OmniWire MCP Server │
│ 22 Core Tools │ 8 CyberSync Tools │ 3 Transports │
└──────┬──────────┴──────────┬──────────┴──────────────────────┘
│ SSH2 (compressed, pooled) │ PostgreSQL
▼ ▼
┌─────────┐ ┌─────────┐ ┌─────────┐ ┌────────────┐
│ Node A │ │ Node B │ │ Node C │ │ CyberSync │
│ storage │ │ compute │ │ GPU │ │ Database │
└─────────┘ └─────────┘ └─────────┘ └────────────┘
Features
MCP Server — 30 Tools
| Category | Tools | Description |
|---|---|---|
| Execution | omniwire_exec, omniwire_broadcast |
Run commands on one or all nodes |
| Monitoring | omniwire_mesh_status, omniwire_node_info, omniwire_live_monitor |
Health, latency, CPU/mem/disk |
| Files | omniwire_read_file, omniwire_write_file, omniwire_list_files, omniwire_find_files |
Full remote filesystem access |
| Transfer | omniwire_transfer_file, omniwire_deploy |
3-mode adaptive transfer engine |
| System | omniwire_process_list, omniwire_disk_usage, omniwire_tail_log, omniwire_install_package |
System administration |
| Services | omniwire_service_control, omniwire_docker |
systemd + Docker management |
| Network | omniwire_port_forward, omniwire_open_browser |
SSH tunnels, remote browsers |
| Advanced | omniwire_kernel, omniwire_shell, omniwire_stream |
Kernel ops, persistent PTY, streaming |
| CyberSync | cybersync_status, cybersync_sync_now, cybersync_diff, cybersync_history, cybersync_search_knowledge, cybersync_get_memory, cybersync_manifest, cybersync_force_push |
Cross-node config synchronization |
SSH2 Connection Layer
- Persistent connection pooling — one SSH2 connection per node, reused for all operations
- Zlib compression — ~60% less data over the wire for text-heavy outputs
- Exponential backoff reconnect — 1s → 2s → 4s → ... → 30s cap with jitter
- Circuit breaker — 3 consecutive failures → 60s cooldown, auto-recovers
- 2MB output guard — prevents memory exhaustion from runaway commands
- Health pings — 30s interval, detects degraded connections (>3s response)
- Status caching — 5s TTL eliminates redundant probes
Adaptive File Transfer Engine
OmniWire automatically selects the fastest transfer mode based on file size:
| Mode | Size Range | Method | Speed |
|---|---|---|---|
| SFTP | < 10 MB | SSH2 native SFTP subsystem | Zero overhead, binary-safe |
| netcat+tar+gzip | 10 MB – 1 GB | Compressed TCP stream | ~70% smaller for text |
| aria2c | > 1 GB | 16-connection parallel HTTP download | Saturates bandwidth |
CyberSync — Config Synchronization
Keeps AI tool configurations (Claude Code, OpenCode, Codex, etc.) synchronized across all your machines:
- 6 tools tracked — claude-code, opencode, openclaw, codex, gemini, paperclip
- File watching — single chokidar instance with batch debounce
- Parallel sync — pushes to all nodes simultaneously via
Promise.allSettled - Parallel hashing — SHA-256 in 50-file batches with streaming for large files
- Conflict resolution — node-ownership model with detailed conflict logging
- Memory bridge — ingests Claude's
memory.db(SQ
Tools (6)
omniwire_execRun commands on one or all nodesomniwire_mesh_statusGet health and latency status of the meshomniwire_read_fileRead a file from a remote nodeomniwire_transfer_fileTransfer files using adaptive modesomniwire_dockerManage Docker containers on remote nodescybersync_sync_nowTrigger cross-node configuration synchronizationEnvironment Variables
OMNIWIRE_CONFIGPath to the OmniWire configuration fileConfiguration
claude_desktop_config.json
{"mcpServers": {"omniwire": {"command": "npx", "args": ["-y", "omniwire"]}}}Try it
→Check the CPU and memory usage across all nodes in the mesh.
→Sync my Claude Code configuration files to all connected servers.
→Restart the docker container named 'web-app' on the production node.
→Read the logs from /var/log/syslog on the database node.
→Transfer the latest backup file from the storage node to the compute node.