node wire

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

Quick start

You need Python 3.13+ and uv. The Installation guide covers the rest.

git clone https://github.com/AOT-Technologies/node-wire.git
cd node-wire
uv sync --frozen --extra agents --dev
cp sample.env .env                  # set NW_ALLOWED_CONNECTORS, e.g. http_generic
export NW_REST_AUTH_DISABLED=true   # local dev only — otherwise /connectors/* and /ready return 503 until auth is configured
MODE=API uv run node-wire

Open http://localhost:8000/docs for the Swagger UI, or the playground for interactive connector demos.

Where to start

• Run it

  Install, configure the NW_* variables, and turn on multi-tenancy.

  Installation · Configuration · Tenancy

• Call a connector

  Use a shipped connector in-process or over REST, per tenant.

  Use a connector · Connector catalog

• Build or generate a connector

  Write one by hand, or generate one from an OpenAPI spec with nw.

  Build a connector · CLI

• Deploy MCP

  Expose connectors to AI agents: one process, per-connector images, or nw gen-stacklok.

  MCP overview

New to the codebase? The reading map gives the order: architecture, domain, seams, the run() pipeline, then topic branches. The reasons behind past decisions are in the ADRs.

Shipped connectors: Google Drive, Salesforce, Slack, SMTP, Stripe, FHIR Epic, FHIR Cerner and HTTP Generic. See the catalog.

Contributing

Contributions are welcome. See the Contributing guide for development setup, quality checks, and DCO requirements, and Changing the docs before you edit a page.