English Français العربية

Node Command

Official registry Search and web

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

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http node-command 'https://mcp.nodecommand.app/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "node-command": {
            "type": "http",
            "url": "https://mcp.nodecommand.app/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. nc-protocol
  2. Namespaces
  3. Consuming the contracts
  4. Testing & Validation
  5. Contributing
  6. Versioning & Compatibility
  7. Related repositories
  8. License

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

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

Frequently asked questions

What is Node Command?

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

How do I install Node Command?

It runs as a remote server. In Claude Code: claude mcp add --transport http node-command 'https://mcp.nodecommand.app/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Node Command need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Node Command open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains Node Command?

It is published by huseyincig. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.