hello@nodemode.dev

Fabric

A server you push becomes an endpoint you can name.

The fabric is the part of NodeMode Dev between your repository & the client that calls your tool. It builds the server, pins it to a DGX B300 node, exposes it over the protocol's own transports & keeps every version you ever shipped.

What a deploy does

  1. Build. You push a repository with a server entry point, Node, Bun or Deno. The official TypeScript SDK runs on all three, so the runtime is your choice, not ours.
  2. Place. You name a pool. A pool is a share of one node's GPU memory (any multiple of one 288 GB GPU), a whole node, or CPU-only. The placement is written into the deploy record & shown on the dashboard.
  3. Expose. The server answers over Streamable HTTP at https://<server>.<org>.nodemode.dev/mcp. If a local client needs stdio, the same build runs on your machine unchanged.
  4. List. Every registered tool, resource & prompt appears in the registry with its schema, as clients will see it on connect. Schema changes between versions are shown as a diff before you promote.

What the fabric runs

Servers built on the official SDKs get the whole surface: tools, resources & prompts; Streamable HTTP & stdio transports; the auth helpers on the server side & OAuth helpers on the client side. Tool & prompt schemas use Standard Schema, so Zod v4, Valibot or ArkType all work. If you wire the server into Express, Fastify, Hono or plain Node HTTP with the SDK's middleware packages, the fabric serves that app as-is.

Fabric services per server
EndpointOne Streamable HTTP URL per server, TLS terminated at the pod edge, Host header validated
RegistryTools, resources & prompts with schemas, per version, with diffs between versions
PoolsNamed GPU shares in 288 GB steps, whole nodes, or CPU-only; quotas visible; placement explicit
SecretsPer-tool secrets scoped at call time; never exported as environment variables a neighbouring tool can read
ObservabilityPer-call latency, GPU occupancy & fabric throughput, streamed to the dashboard or your own OTLP collector
RollbacksEvery deploy is a version; any version restores with its schema & its secrets scope in one command
NetworkEach node has eight 800 Gb/s ConnectX-8 ports on the cluster network & two BlueField-3 DPUs for storage & management

What the fabric will not do

  • Invent a transport. If it is not stdio or Streamable HTTP as the spec defines them, it does not run here.
  • Move a server without a deploy. Placement changes are versions too.
  • Share a GPU behind your back. A pool is either yours or not scheduled.
See pricingWrite a server