Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.
One address for any MCP client. Your key stays in your Odel vault.
Not assessed yet.
Odel charges nothing per call. The publisher may charge for its own service.
| Access to | Read | Change |
|---|---|---|
| Mcp | Not stated: mcp:access | |
From the sign-in at auth.nodecommand.app, as the endpoint publishes it. You approve it there.
Odel could not list its tools without signing in.
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.
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)
# As an npm dependency
npm install nc-protocol
Import JavaScript bindings directly:
import {
MCP_TOOL_CONTRACT_VERSION,
MCP_TOOL_MANIFEST_FINGERPRINT,
MCP_TOOL_NAMES,
HOST_POLICY_CAPABILITY_NAMES
} from 'nc-protocol';
JSON schemas can also be imported by subpath:
import helloSchema from 'nc-protocol/agent/hello.schema.json' with { type: 'json' };
import toolsIndex from 'nc-protocol/mcp/tools/index.json' with { type: 'json' };
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/*.mjs
The test suite validates:
mcp/tools/index.json, and tool count.sha256 manifest fingerprint.See CONTRIBUTING.md for detailed guidelines on how to propose new tools, update schemas, recompute fingerprints, and submit pull requests.
Apache-2.0 — see LICENSE.