mcpField
N
Node Command

Node Command

Remote
github.com/huseyincigDeveloper Tools0Updated today
Repository

About Node Command

Node Command is a declarative repository of public wire contracts, MCP tool schemas, and agent protocols for consumers building or maintaining Node Command integrations. Its versioned schemas and generated JavaScript bindings provide an auditable contract source without runtime dependencies.

Key features

  1. 01MCP tool schemas and canonical manifest
  2. 02Hub-to-agent wire protocol definitions
  3. 03Host policy and capability schemas
  4. 04Browser and egress policy schemas
  5. 05Generated JavaScript bindings
  6. 06Contract validation tests

Use cases

  1. 01Vendor pinned contracts in Node Command consumers
  2. 02Check MCP tool definitions against the canonical manifest
  3. 03Validate schema and binding consistency

MCP support

Defines the public MCP tool schemas and canonical manifest used by Node Command integrations; it is a contract repository, not an MCP server implementation.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.nodecommand.app/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

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.

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.

Namespaces

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)

Consuming the contracts

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.git

Import 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.

Testing & Validation

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:

  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

Related repositories

  • NodeCommand — product documentation, client examples, and manifests.
  • nc-agent — the open-source host agent and CLI installer that implements these contracts.

License

Apache-2.0 — see LICENSE.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.