See what is happening
Read overview, schema, queue depth, bounded logs and event receipts. Export a diagnostic archive for investigation.
v0.48.7 BETA Built to reconnect
Your data.
Your data.
Closer together.
From the factory floor to your central server. Keep MySQL data moving across Windows edge networks, with control that stays in your hands.
A closer lookIllustrative preview
NodeBridgeWORKSPACE / 01YOUR SYNC NETWORK
Every node. One view.
Central server
MySQLserver-001EDGE NETWORK02
Production line A
Syncingedge-001Production line B
Syncingedge-002Bidirectional rules. Explicit destinations.
RULE WORKSPACE
Names that make sense.
Production events
production-eventsSource
factory_edge.eventsDestination
factory_center.eventsPrimary key
idDirectionBidirectional
A new display name. The same stable identity.
CONNECTION RECOVERY
Ready to pick up again.
- 01Connection interrupted
Keep unacknowledged messages available for retry.
- 02Rebuild the connection
Replace the failed channel and publisher.
- ✓Resume synchronization
Retry with event idempotency after connectivity returns.
No manual Agent restart for this recovery path.
01 — 03Explore the tabs above ↑
Built on a familiar foundation
MySQLCanal CDCRabbitMQGoWails
⌘ MODEL CONTEXT PROTOCOL
Your AI assistant.
Connected to your operations.
Give your MCP client structured access to NodeBridge. Inspect a queue, review a rule, or track an alignment task using the same management capabilities as the application.
What would you ask?01 — 03
Local stdio or remote SSH. Your client stays in control of the conversation.
YOU ASK
Why has edge synchronization stopped progressing?
TOOLS THE CLIENT CAN CALLJSON-RPC · stdio
- 01
nodebridge_overview - 02
nodebridge_queue_status - 03
nodebridge_logs - 04
nodebridge_event_status
Correlate process status with queue depth and event evidence. A running process alone does not prove healthy synchronization.
Move from insight to action
Validate and save configuration, manage rules, control the Agent and retry failed events. Data mutations use structured plans and explicit confirmation.
Work across your nodes
Add one client entry per Windows node. Use local stdio or SSH from Windows or Mac, with the configuration-owning account.
CONNECT YOUR MCP CLIENT
Start with a local connection.
Save a complete configuration and enable MCP in NodeBridge. Run the client as the Windows account that owns the configuration. Adapt command and args to your client's format.
MCP tool reference ↗Remote SSH setup ↗{
"mcpServers": {
"nodebridge": {
"command": "C:\\Program Files\\NodeBridge\\app\\SyncAgent.exe",
"args": [
"mcp-stdio",
"-config",
"C:\\ProgramData\\NodeBridge\\config.yaml"
]
}
}
}Built-in boundaries. No MCP HTTP listener, arbitrary shell or raw SQL. Configuration validation, redacted output and write auditing remain in place. Initial alignment requires stopped Agents on every participant, explicit confirmation and status polling; running is not completion.
DESIGNED FOR THE EDGE
Complex networks.
A clearer way to manage them.
Practical tools for the moments that matter: configuring a rule, losing a connection, rolling out an update.
01 / RESILIENCE
Reconnect. Resume.
Failed RabbitMQ connections are rebuilt automatically, so the Agent can resume synchronization when connectivity returns.
Automatic reconnection
02 / CLARITY
Less scrolling. More context.
Compact rule editing and prominent display names keep configuration readable, without replacing IDs or existing alignment records.
Human-readable rule names
03 / CONTINUITY
Move forward, together.
The installer updates configured NodeBridge system databases. If a migration fails, installation completion is blocked.
Built-in system migrations
FROM DOWNLOAD TO DEPLOYMENT
Your network.
Your next step.
Start with the guide. Keep the configuration explicit. Validate in your own environment.
Read release notes- 01
Prepare your environment
Install MySQL separately, assign unique node IDs, and back up configuration, rules and databases.
- 02
Install and configure
Run the Windows installer as administrator. Define your source and target databases, tables and columns.
- 03
Validate your deployment
Check alignment, CRUD and recovery in your environment. This beta has isolated three-Agent coverage, not a production SLA.
MySQL synchronization for Windows edge networks
Synchronize MySQL between edge nodes and a central server with bidirectional mappings, automatic reconnection and MCP tools for AI-assisted operations. Windows installer available.