MCP server: One MCP server.

Node Command

@huseyincigMCP server · External

Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.

Computer controlv0.26.109Apache-2.0JavaScript
Freeno charge per call

One address for any MCP client. Your key stays in your Odel vault.

What it does

  1. Reads
  2. Writes
  3. High impact

Not assessed yet.

What it costs

Free

Odel charges nothing per call. The publisher may charge for its own service.

What it asks for at sign-in

Access toReadChange
McpNot stated: mcp:access

From the sign-in at auth.nodecommand.app, as the endpoint publishes it. You approve it there.

Tools

None listed · checked 12 Oct 2026

Odel could not list its tools without signing in.

Try it in the Inspector
README1 min read

nc-protocol

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.


Namespaces

text
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)

Installation & Consumption

bash
# As an npm dependency
npm install nc-protocol

Import JavaScript bindings directly:

javascript
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:

javascript
import helloSchema from 'nc-protocol/agent/hello.schema.json' with { type: 'json' };
import toolsIndex from 'nc-protocol/mcp/tools/index.json' with { type: 'json' };

Testing & Validation

nc-protocol has zero runtime dependencies and uses the native Node.js test runner:

bash
# 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:

  1. Presence of all required namespace files.
  2. Exact matching between tool definitions, mcp/tools/index.json, and tool count.
  3. Cryptographic consistency of the canonical sha256 manifest fingerprint.
  4. Schema parse validity and schema draft conformance.
  5. Binding parity with declarative contract files.

Contributing

See CONTRIBUTING.md for detailed guidelines on how to propose new tools, update schemas, recompute fingerprints, and submit pull requests.


Versioning & Compatibility


License

Apache-2.0 — see LICENSE.

Similar modules

Browse Computer control