nock
An MCP server that sits between coding agents and local tools, using a tiny on-device model to route tool calls and requiring confirmations for destructive actions, while only exposing four tools to the host.
README
Nock

Nock sits between a coding agent (ChatGPT / Codex, Cursor, Claude Desktop, …) and your local tools.
The cloud model does the thinking. A tiny on-device model (Needle) tries to pick the right tool. Destructive actions wait for a confirm token. If Needle is unsure or the request is off-topic, Nock refuses without sending your tool list to the cloud.
The host only sees four tools: nock.resolve, nock.call, nock.search, nock.status.
Install
python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
Optional — so nock.resolve can pick tools instead of always refusing:
pip install -e ".[needle]"
That extra pulls JAX. First resolve also downloads the ~14 MB Needle engine.
Point Codex / ChatGPT desktop at it
They share ~/.codex/config.toml. Easiest:
codex mcp add nock -- /ABS/PATH/nock/.venv/bin/nock serve --warmup
Use the absolute path to the venv nock binary. Restart the app, then /mcp should list nock.
Your tools live here, not in Codex
~/.config/nock/config.toml:
[discover]
include_host_configs = false
[servers.fs]
command = "npx"
args = ["-y", "@modelcontextprotocol/server-filesystem", "/ABS/PATH/to/a/folder"]
default_risk = "safe"
[servers.fs.tools.write_file]
risk = "destructive"
Keep Codex’s MCP list to Nock only. Nock starts the filesystem (and anything else you add).
How the host should use it
nock.resolvewith the user text.fast→nock.callthe returned envelope.shortlist→ pick one of the listed tools, thennock.call.escalate→ answer without tools. Do not callnock.search.- If
nock.callreturnstype: nock.confirm, call again withconfirm=trueandconfirm_token.
Reads should not confirm. Writes should.
Commands
nock serve # stdio MCP server (what the host launches)
nock status # dry config check (does not talk to a running serve)
nock doctor # binaries, Needle, duplicate servers
nock hosts # copy-paste snippets for Codex, Claude, Cursor, Continue
nock index # warm Needle’s tool index
Tests
pytest
MIT. Needle is a separate project from Cactus Compute.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.