Privacyscrubber MCP Server

Zero-Trust PII & secrets sanitizer. Locally scrubs data in-memory before sending context to LLMs.

Local serverstdioGo

What is the Privacyscrubber MCP server?

If you already use Privacyscrubber, the privacyscrubber mcp server is the piece that lets your assistant work with it directly. Zero-Trust PII & secrets sanitizer. Locally scrubs data in-memory before sending context to LLMs.

What the server does

All sensitive parameters, identifiers, and variables are intercepted locally inside your machine's RAM. They are replaced by tokens (e.g. [EMAIL_1]) before being sent to the AI. Once the AI responds, the tokens are safely swapped back to original values in your local context.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Cursor — 1. Go to Settings → Features → MCP Servers. 2. Find privacyscrubber and click Edit. 3. Add the environment variable
  • Windsurf — The Windsurf tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: PRIVACYSCRUBBER_KEY, YOUR_OPTIONAL_PRO_LICENSE_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Where it fits

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

This entry was verified against Privacyscrubber's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • 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.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
Cursor1. Go to **Settings → Features → MCP Servers**. 2. Find privacyscrubber and click **Edit**. 3. Add the environment variable: PRIVACYSCRUBBER_KEY=YOUR_LICENSE_KEY_HERE. 4. Restart Cursor.
WindsurfThe Windsurf tool exposed by this server.

How to install the Privacyscrubber MCP server

{
  "mcpServers": {
    "privacyscrubber": {
      "command": "npx",
      "args": ["-y", "@privacyscrubber/mcp-server"],
      "env": {
        "PRIVACYSCRUBBER_KEY": "YOUR_LICENSE_KEY_HERE"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
PRIVACYSCRUBBER_KEYCredential the server authenticates with.Yes
YOUR_OPTIONAL_PRO_LICENSE_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Privacyscrubber to Cursor.
  • Use Privacyscrubber to Windsurf.

Frequently asked questions

It connects Privacyscrubber to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Cursor, Windsurf) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Privacyscrubber directly.