Node Wire

Node Wire is a three-layer Python platform that runs connector adapters (Google Drive, SMTP, Stripe, FHIR, etc.) and exposes them over REST, gRPC, or MCP. It provides a consistent execution contract with built-in validation, resilience, and telemetry.

Prerequisites

Before getting started, make sure you have:

Quick Start

1. Install

git clone https://github.com/AOT-Technologies/node-wire.git
cd node-wire
uv sync --frozen --all-extras --dev

(Requires uv. See Installation for lockfile update workflow.)

2. Configure

Copy the sample environment file and add your NW_ALLOWED_CONNECTORS:

# Linux/macOS/PowerShell
cp sample.env .env

# Windows (CMD)
copy sample.env .env

(Edit .env and set NW_ALLOWED_CONNECTORS=http_generic or others)

3. Run Grafana/OpenTelemetry (optional)

For telemetry visualization, start the Grafana stack before running the application:

cd grafana && docker compose up -d

4. Run

Bash (Linux/macOS):

# Using uv (recommended)
MODE=API uv run node-wire

# Using python
MODE=API python -m bindings_entrypoint

PowerShell (Windows):

# Using uv
$env:MODE="API"; uv run node-wire

# Using python
$env:MODE="API"; python -m bindings_entrypoint

(Modes: API, GRPC, MCP)

Open http://localhost:8000/docs to see the Swagger UI.

5. Playground

The platform includes an interactive web playground at http://localhost:8000/playground/ (available when the REST API is running).

Build Packages (Wheels)

Before building Docker images, build the Python packages as binary wheels:

bash scripts/build-packages.sh

See docs/packaging.md for details on the wheel build lifecycle.

Build MCP Server Images

Use this workflow when you want Docker images for the individual MCP servers such as Google Drive, SMTP, Stripe, Salesforce, or Slack.

Build prerequisites

Before building images, make sure:

• Docker is installed and available on your shell path.
• You are running commands from the repository root.
• Local wheels have been built first.

See docs/local-packages-to-images.md for the full package -> image workflow and required wheel artifacts per image.

Build all MCP server images

All MCP server images are built from the repository root using the automation script:

./scripts/build-mcp-images.sh

To tag with a specific version (defaults to the version in pyproject.toml):

./scripts/build-mcp-images.sh --version 1.0.0

This produces images tagged as both latest and the version string:

Build one image manually

To build a single image manually from the repo root:

# Google Drive only
docker build -f docker/google-drive/Dockerfile -t nw-google-drive:latest .

# Epic FHIR only
docker build -f docker/fhir-epic/Dockerfile -t nw-smartonfhir-epic:latest .

# Cerner FHIR only
docker build -f docker/fhir-cerner/Dockerfile -t nw-smartonfhir-cerner:latest .

# SMTP only
docker build -f docker/smtp/Dockerfile -t nw-smtp:latest .

# Stripe only
docker build -f docker/stripe/Dockerfile -t nw-stripe:latest .

# Salesforce only
docker build -f docker/salesforce/Dockerfile -t nw-salesforce:latest .

# Slack only
docker build -f docker/slack/Dockerfile -t nw-slack:latest .

Note: The build context must be the repository root (.) so the COPY src/ and COPY config/ instructions resolve correctly.

Run MCP Servers with Docker Compose

Compose prerequisites

Before starting the MCP containers, make sure:

• The MCP server images have already been built locally.
• Your .env file is populated with the credentials needed by the connectors you want to run.

docker-compose.mcp.yml starts all MCP servers as stdio containers in one command. This is useful for local validation before configuring ToolHive.
Each service pins NW_ALLOWED_CONNECTORS to its own connector so a broad value in .env does not make per-connector images import optional dependencies they do not contain.

# Ensure local wheels exist and your .env is populated, then:
docker compose -f docker-compose.mcp.yml up --build

To start only a specific server:

docker compose -f docker-compose.mcp.yml up --build nw-smartonfhir-epic

Documentation

For more detailed information, please refer to the following guides:

• Architecture — Layered design and data flow.
• Installation — Detailed setup and prerequisites.
• Configuration — Environment variables and connectors.yaml.
• Connectors Guide — How to use and build connectors.
• MCP Integration — Using Node Wire with AI agents.
• Troubleshooting — Common errors and fixes.
• MCP Servers & Docker — Deploying individual connectors as MCP servers.
• Packaging & Publishing — Wheel builds and CI flow.
• Release Rollback — PyPI yank and corrective release procedure.
• Code Quality & Compliance — Ruff, Mypy, pre-commit, REUSE, and dependency compliance.
• Privacy — Data handling and logging guidance.
• HIPAA Considerations — Deploying Node Wire in regulated healthcare environments.
• ToolHive Agent Scenario — End-to-end FHIR → Google Drive → email workflow.
• Changelog — Release history.

Developer docs

• Individual connector MCP servers (ToolHive): docs/mcp-servers.md
• Creating a new connector: docs/connectors.md
• Code quality/compliance (Ruff, Mypy, REUSE, pip-audit): docs/code-quality-compliance.md
• Quality/security gates (Bandit, CodeQL): docs/quality-security-gates.md

Contributing

Contributions are welcome! Please read CONTRIBUTING.md for
the development setup, quality checks, and PR conventions, and our
Code of Conduct.

Security

To report a vulnerability, please follow our Security Policy. Do
not open a public issue for security reports.

License

This project is licensed under the Apache License 2.0.
See the LICENSE file for details.