An MCP server configuration for the NeatContext plugin, started with Node.js from a local bridge file. MCP connects an AI agent to external tools.

It launches the local NeatContext bridge; the specific capabilities are not provided in the available information.

The configuration shows how to start the server, but does not describe the tools or jobs it exposes.

neatcontext — MCP server by XTSoftwareLabs

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add mcp/xtsoftwarelabs/neatcontext-plugins/neatcontext-neatcontext

Clone the repo

git clone --depth 1 https://github.com/XTSoftwareLabs/neatcontext-plugins

Made for: Claude Code, Codex, Cursor, Gemini CLI, OpenCode.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

neatcontext scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

codex-marketplace/plugins/neatcontext/.mcp.json · 9 lines

What it actually says

{
  "neatcontext": {
    "command": "node",
    "args": [
      "./src/codex/mcp-bridge.mjs"
    ],
    "cwd": "."
  }
}

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 9 lines scan A a8e2a6b1c195

Subscribe to this mod's changes

neatcontext is an MCP server published in the GitHub repository XTSoftwareLabs/neatcontext-plugins (13 stars, last pushed 10d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

ai-context claude-code claude-code-plugin claude-code-skills claude-plugin claude-skills

neatcontext

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other mcp servers, from other repositories

qector-library

qector-desktop

hex-line-mcp

eu-ai-act

docs-langchain

reference-langchain