MCP Code Sanitizer MCP Server

Create .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally):. The mcp code sanitizer mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 1 defined tool rather than through you.

Its toolset

Everything the assistant can do here goes through one of these:

• Cursor — Create .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally):

Adding it to your client

mcp-code-sanitizer on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration

You will need one environment variable: GROQ_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Code Sanitizer's toolset — Cursor — is a fair guide to whether it matches your workflow. It is maintained by notasandy; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp code sanitizer mcp server does with a few real requests.