nc-tools-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@nc-tools-mcpshow me the git status and uncommitted changes in this repo"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
nc-tools — the Typed Machine API for coding agents
A terminal-free machine interface: every operation the terminal used to provide (files, search, patches, git, processes, tests, packages, network) is a typed tool with structured inputs, structured outputs, structured errors, and a full append-only event journal. One static Rust binary speaks MCP over stdio.
Thesis: the terminal is the machine's untyped API. Replace it with a typed one and agents become verifiable, replayable, measurable, and safer — without changing their model or harness.
Quick start
Requires Rust (stable) and Node ≥ 20 (for the test/dev harnesses only — the kernel itself has zero runtime dependencies).
git clone https://github.com/ncdevshiv/nc-tools.git
cd nc-tools
cargo build --release -p nct-mcp # → target/release/nc-tools-mcp(.exe)
npm run conform # 27 protocol conformance cases, black-boxMount it in any MCP client (ZCode, Claude Desktop, Cursor-style hosts, custom
loops) — see docs/MCP-CONFIG.md. Point the command at
target/release/nc-tools-mcp with your workspace root as the only argument, or
run npm run install:bin to copy it to ~/.local/bin and use that stable path.
Related MCP server: core-agent-mcp
What's in the box
Path | What it is |
| The Rust workspace — 8 crates; |
| Language-neutral protocol cases ( |
| Node test suite driving the binary as a black box over MCP stdio |
| Task suite, verifier validator, and agent-run harness (real verifiers, journaled transcripts) |
| Conformance runner, cross-audit, stub-audit, golden exporter, kernel client |
| Protocol spec, MCP client config, internet-tool design, audit trail |
The tool surface (60 typed tools)
fs.*— read/readMany/readRange, write/writeMany, append, copy, list, tree, stat, mkdir, delete, movepatch.apply/applyMany— search/replace edits with exactness guardssearch.grep/files/replace/semantic,code.symbols,text.diffgit.status/diff/add/blame/commit/log/branch/checkout/push/pullproc.spawn/start/status/readOutput/stop/list/kill/runScript/watch— argv-typed, no shelltest.run(node, pytest),pkg.add/list/scripts/runScriptnet.http/probePort/fetch/robots/search— see docs/INTERNET-TOOLS.mdenv.get/set/list,sys.snapshot/rollback/listSnapshots/journal/workspace/doctor,batch.execute
The frozen machine-readable export is conformance/golden/tools.json
(regenerate with npm run golden; changes must be deliberate). The full
contract — error taxonomy, journal schema, transport bindings — is
docs/PROTOCOL.md.
Principles
Typed in, typed out. Tools return structured results and structured errors with machine-readable remediation hints. No stdout scraping.
Everything is journaled. Every tool call and result is an event in
<workspace>/.nc-tools/journal.jsonl. Sessions are replayable and auditable.Mutations are deliberate. Writes go through validated patches (search/replace blocks with occurrence counts). No silent overwrites.
No shell. There is no
exec/bash tool.proc.spawnis argv-typed. If a task requires a shell, that is a tool to design, not an escape hatch.
Verification gates
Every claim in this repo is machine-checked:
cargo test # Rust unit + integration suites
npm run test:node # black-box protocol/behavior suite over MCP stdio
npm run conform # language-neutral conformance (27 cases)
npm run crossaudit # audits THIS repo through its own MCP server
npm run audit # stub/TODO/mock/placeholder scan (exit 1 on findings)
npm run verify:verifiers # bench verifiers: untouched→fail, solved→pass, wrong→rejectedLicense
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Your org's AI agents, tasks, runs, search, and brain files as MCP tools and resources.
Governed app access for AI agents: 1,000+ apps & 12,000+ tools via Code Mode MCP.
MCP-first toolbox for agents: KV storage, auth, queue, and utility tools. Free in early access.
Pay-per-use tool marketplace for AI agents. Search, price-check, and call APIs via MCP.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenance45+ first-class, OS and backend specific MCP tools that let AI coding agents create, manage, read, edit, and write files inside dev containers, keeping your machine clean and your environment reproducible and deploy-friendly. Use local Docker, GitHub Codespaces, Azure, AWS, Google Cloud or Kubernetes seamlessly!26MIT
- AlicenseNot gradedqualityCmaintenanceRemote execution layer for agentic systems exposing 64 production tools via MCP for file, network, system, text, git, crypto, and monitoring operations.MIT
- FlicenseNot gradedqualityDmaintenanceProvides 180+ tools for full system control including terminal, Git, Docker, Kubernetes, VMs, BIOS, kernel, cybersecurity, AI, and cloud, designed to work with MCP clients like Cursor and Claude Desktop.
- FlicenseNot gradedqualityCmaintenanceEnables AI coding assistants to manage persistent memory, search project context, generate tests, review architecture, and orchestrate workflows through 15 MCP tools, enhancing context-aware code generation.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ncdevshiv/nc-tools'
If you have feedback or need assistance with the MCP directory API, please join our Discord server