Skip to main content
Language v0.2.0 · Preview

Bounded N/M MCP tools

Connect agents to seven versioned local N/M tools with strict protocol negotiation, hostile-client validation, bounded carriers and byte-identical Core/stdio behavior.

Public npm installation

Connect the local MCP server

Configure a client that supports local stdio MCP servers. Seven tools inspect and run supplied N/M source; this package is not an AI model or a hosted chat service.

Requires Node.js 20 or newer. Release checks use Node.js 22.23.1.

npm package 0.2.1 targets N/M language 0.2.0. next selects the preview channel and can change; use @0.2.1 to reproduce this release. An untagged install selects latest. The VS Code extension has a separate distribution version.

npm install --global @nm-lang/mcp@next

To pin this release:

npm install --global @nm-lang/mcp@0.2.1

MCP client configuration for a pinned package version

{
  "mcpServers": {
    "nm": {
      "command": "npx",
      "args": [
        "-y",
        "@nm-lang/mcp@0.2.1"
      ]
    }
  }
}

Examples run on a local simulator. Installation does not establish physical QPU access or make every capability stable.

Personal, educational and commercial use is free. QuantumSoftware retains rights to its package code; modification and redistribution require separate permission. Your N/M programs and results remain yours. Read LICENSE.txt in the installed package.

Versioned bounded MCP tool contract

The stateful Core handler and standalone newline-delimited stdio server share byte-identical JSON-RPC responses. A hosted server negotiates the MCP protocol before exposing seven local, closed-world N/M tools.

2026-07-26
contract
2025-06-18
protocol
0.1
schema

Versioned tool schemas

Every tool publishes a JSON Schema 2020-12 object with required fields, no unknown properties, bounded scalar ranges, behavior annotations, and explicit contract and schema versions. Runtime validation also measures UTF-8 bytes.

Protocol lifecycle

Hosted sessions fail closed before initialize, reject unsupported protocol versions and duplicate initialization, accept the initialized notification, and return stable JSON-RPC plus NM-MCP error evidence.

Local execution boundary

Tools do not access networks, credentials, repositories, or arbitrary files. Parse, simulation, training, export, optimization, examples, and curated package discovery run only against request data and bundled registries.

Carrier limits

Oversized input lines are discarded before JSON dispatch. Code, query, structured tool data, and complete responses have independent fail-closed budgets; output overflow becomes NM-MCP-007 instead of a truncated carrier.

Shared capability visibility

Preview: Usable preview, not a stable compatibility promise; review the listed limitations before production use. Experimental contracts may change without the stable deprecation promise. New sessions enable the default language profile; other features require opt-in. Saved settings are preserved.

Local simulator result

Local or synthetic execution only; this result is not evidence of physical-device performance or quantum advantage. Requires an explicit provider/device path and retained backend provenance; simulator output never upgrades to hardware evidence.

1 MB
input line
200 KB
code
256 B
query
400 KB
tool data
1 MB
response

JSON-RPC / stdio

npm run nm:mcp

{ "jsonrpc": "2.0", "id": 1, "method": "initialize", "params": { "protocolVersion": "2025-06-18" } }
nm_parsenm_runnm_trainnm_exportnm_optimizenm_examplesnm_capabilities
NM-MCP-001NM-MCP-002NM-MCP-003NM-MCP-004NM-MCP-005NM-MCP-006NM-MCP-007NM-MCP-008

Contract 0.2 covers newline-delimited stdio and the versioned seven-tool registry. Remote transports, prompts/resources, sampling, server-side persistence, secrets, arbitrary filesystem access, and third-party MCP client certification remain outside this candidate.