The Nothing

The idea: sometimes less is more

Most MCP servers race to do more: connect to more databases, read more files, call more APIs. That's great when you need it. But for a lot of simple scenarios, you don't — and every extra connection is one more credential to manage, one more thing that can break, and one more way an AI can touch data it shouldn't.

The Nothing takes the opposite approach. It connects to no database, reads no dataset, makes no network calls, writes nothing to disk and remembers nothing between calls. What it does provide is a clean, stable seam — a tool contract your AI can talk to — so the AI is never wired directly to your data layer.

That's why we call it Mr. Decoupler. He stands politely between your AI and your data, hands back exactly what he was given, and lets you decide later (or never) what should actually sit behind him.

Related MCP server: MCP API Tool Demo

Why use a server that does nothing?

What's inside

Every tool is annotated read-only, idempotent, non-destructive and closed-world, so clients that respect MCP tool annotations can run them without confirmation prompts. search and fetch exist so search-oriented clients such as ChatGPT connectors accept the server; they find nothing, by design.

Install

Node.js 18+ is the only requirement.

npx -y the-nothing-mcp           # stdio (local clients)
npx -y the-nothing-mcp --http    # Streamable HTTP at http://0.0.0.0:3000/mcp (remote clients)

Options: --port 3000, --host 0.0.0.0, or env THE_NOTHING_TRANSPORT=http, PORT, HOST.

Connect it to your AI

Local clients (stdio)

Most local clients use the same mcpServers block:

{
  "mcpServers": {
    "the-nothing": {
      "command": "npx",
      "args": ["-y", "the-nothing-mcp"]
    }
  }
}

VS Code + GitHub Copilot — install the The Nothing extension from the Marketplace (zero config), or add .vscode/mcp.json:

{
  "servers": {
    "the-nothing": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "the-nothing-mcp"]
    }
  }
}

OpenAI Codex CLI — ~/.codex/config.toml:

[mcp_servers.the-nothing]
command = "npx"
args = ["-y", "the-nothing-mcp"]

Remote clients (Streamable HTTP)

ChatGPT, Grok, claude.ai custom connectors and hosted agent APIs reach MCP servers over HTTPS, so run The Nothing in HTTP mode somewhere public:

npx -y the-nothing-mcp --http --port 3000
# or
docker build -t the-nothing . && docker run -p 3000:3000 the-nothing

Put it behind HTTPS (any host, or a tunnel such as Cloudflare Tunnel or ngrok for testing), then use https://your-host/mcp:

The HTTP server is stateless (no sessions, no auth, nothing stored), answers GET /health, and sends permissive CORS headers. It needs no secrets, because there is nothing to protect.

Use it as a library

import { createServer } from "the-nothing-mcp";
const server = createServer(); // a fresh McpServer that does nothing

Development

npm install
npm test               # exercises every tool over stdio and HTTP
npm run build:vscode   # bundles the server into the VS Code extension

See PUBLISHING.md for releasing to npm, the official MCP Registry and the VS Code Marketplace.

FAQ

Does it really do nothing? Yes. Read src/server.js; it's short. There is no I/O apart from the MCP transport itself.

Then why not just have no server? Because a stable contract is worth something. The Nothing lets your AI, prompts and configs depend on an interface instead of an implementation. When you're ready for real data, replace Mr. Decoupler with a server that exposes the same tools, and nothing else has to change.

Is it safe to give to an autonomous agent? It's about as safe as software gets: it cannot reach anything.

License

MIT

mcp-name: io.github.Meador793/the-nothing