Node Command MCP server
Commit Oct 29, 2026Exposes a fleet of files, shell, processes, and browser capabilities to AI hosts via standardized MCP tool schemas.
Also known as huseyincig/nc-protocol, nc-protocol
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.26.125
- Last commit
- Oct 29, 2026
- License
- Apache-2.0
What is Node Command MCP?
Node Command exposes a fleet of files, shell, processes, and browser capabilities to AI hosts via standardized MCP tool schemas.
Summary generated from the project's README
About Node Command MCP server
Node Command provides a standardized set of Model Context Protocol schemas that allow AI hosts to interact with files, shell environments, processes, and browser capabilities. Instead of a traditional runtime server, this repository serves as the canonical source of truth for the wire contracts and tool definitions used by the Node Command hub and the nc-agent runtime. Developers use these declarative schemas to ensure their client integrations remain compatible with the platform's evolving capabilities.
Integration requires vendoring the repository at a pinned commit SHA rather than installing a runtime dependency. Users can import JavaScript ESM bindings or JSON schemas directly to access tool names, host policy capability names, and contract versions. This approach ensures that contract changes are explicit and auditable for anyone building against the nc-agent or the Node Command hub. The system relies on authenticated tools/list responses to determine which specific tools are available to a user based on their role and scope.
What you can do with it
- 1Implement standardized agent communicationA developer can use the agent namespace to build a wire protocol for hello, welcome, request, reply, and heartbeat messages.
- 2Integrate browser and egress policiesDevelopers can import specific JSON schemas to manage how an AI client handles browser interactions and egress policies.
Written from the project's README. Every use case is checked against a quote from it.
How to install Node Command MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Node Command MCP in Claude Code
$ claude mcp add --transport http nc-protocol https://mcp.nodecommand.app/mcpInstall Node Command MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"nc-protocol": {
"url": "https://mcp.nodecommand.app/mcp"
}
}
}Install Node Command MCP in VS Code
.vscode/mcp.json
{
"servers": {
"nc-protocol": {
"type": "http",
"url": "https://mcp.nodecommand.app/mcp"
}
}
}Install Node Command MCP in VS Code CLI
$ code --add-mcp '{"name":"nc-protocol","type":"http","url":"https://mcp.nodecommand.app/mcp"}'Install Node Command MCP in Codex
$ codex mcp add nc-protocol --url https://mcp.nodecommand.app/mcpInstall Node Command MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.nc-protocol] url = "https://mcp.nodecommand.app/mcp"
Install Node Command MCP in Gemini CLI
$ gemini mcp add -s user --transport http nc-protocol https://mcp.nodecommand.app/mcpInstall Node Command MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"nc-protocol": {
"url": "https://mcp.nodecommand.app/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablehuseyincig/nc-protocol is public and reachablegithub.com/huseyincig/nc-protocol ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-29github.com/huseyincig/nc-protocol ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubnc-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/ Canonical authoring definitions and contract 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.
The manifest counts canonical authoring definitions, not the number of tools
available to a particular connected user. The hosted platform composes these
definitions into its public nc_ surface and filters discovery by role and scope.
Use that server's authenticated tools/list response for callable names and
schemas; do not invoke an authoring identifier merely because it appears here.
Internal operation identifiers and the agent wire protocol remain distinct.
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:
- 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.
Contributing
See CONTRIBUTING.md for detailed guidelines on how to propose new tools, update schemas, recompute fingerprints, and submit pull requests.
Versioning & Compatibility
- VERSIONING.md — SemVer lifecycle and breaking-change policies.
- COMPATIBILITY.md — Current contract generations and rollout gates.
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.
Node Command MCP questions
How do I add Node Command MCP to Claude Code?
Run claude mcp add --transport http nc-protocol https://mcp.nodecommand.app/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Node Command MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How do I consume the Node Command contracts?
Consumers should vendor the repository at a pinned commit SHA and import from the vendored tree, as there is no runtime dependency to install.
Can I use the tool names found in the manifest directly?
No, you should use the authenticated tools/list response from the server for callable names and schemas, as the manifest counts definitions rather than available tools.