Public wire contracts, Model Context Protocol (MCP) tool schemas, and agent protocol definitions for Node Command.
This repository is the canonical source of truth for the public Node Command contracts. It contains strictly declarative schemas and contracts: no proprietary server code, no database schemas, and no secrets.
Consumers — the Node Command hub, the
nc-agent runtime, and client
integrations — vendor this repository at a pinned commit, so contract
changes here are explicit and auditable.
agent/ Hub ↔ Agent wire protocol (hello / welcome / request / reply / heartbeat)
mcp/ Model-facing MCP surface (tool schemas + canonical tool manifest)
policy/ Public host-policy projection + capability names
browser/ Public browser and egress policy schemas
bindings/ Generated language bindings (JavaScript ESM)
There is no runtime dependency to install: consumers vendor this repository at a pinned commit SHA and import from the vendored tree.
git clone https://github.com/huseyincig/nc-protocol.gitImport the JavaScript bindings directly:
import {
MCP_TOOL_CONTRACT_VERSION,
MCP_TOOL_MANIFEST_FINGERPRINT,
MCP_TOOL_NAMES,
HOST_POLICY_CAPABILITY_NAMES
} from './nc-protocol/bindings/javascript/contracts.mjs';JSON schemas can be imported by path:
import helloSchema from './nc-protocol/agent/hello.schema.json' with { type: 'json' };
import toolsIndex from './nc-protocol/mcp/tools/index.json' with { type: 'json' };The current contract version, fingerprint, and capability list are pinned in
mcp/contract-version, mcp/fingerprint, and policy/capability-names;
the current generation and rollout rules are in
COMPATIBILITY.md.
nc-protocol has zero runtime dependencies and uses the native Node.js
test runner:
# Clone the repository
git clone https://github.com/huseyincig/nc-protocol.git
cd nc-protocol
# Run test suite
npm test
# Or:
node --test tests/*.mjsThe test suite validates:
- Presence of all required namespace files.
- Exact matching between tool definitions,
mcp/tools/index.json, and tool count. - Cryptographic consistency of the canonical
sha256manifest fingerprint. - Schema parse validity and schema draft conformance.
- Binding parity with declarative contract files.
See CONTRIBUTING.md for detailed guidelines on how to propose new tools, update schemas, recompute fingerprints, and submit pull requests.
- VERSIONING.md — SemVer lifecycle and breaking-change policies.
- COMPATIBILITY.md — Current contract generations and rollout gates.
- NodeCommand — product documentation, client examples, and manifests.
- nc-agent — the open-source host agent and CLI installer that implements these contracts.
Apache-2.0 — see LICENSE.