redacted-context-mcp

# Redacted Context MCP Give coding agents useful local project context without exposing raw client names, people, email addresses, URLs, phone numbers, secrets, or meaningful filenames. `redacted-context-mcp` is a read-only-by-default MCP server and CLI. It lets an agent search, navigate, and read useful content from a private local folder while replacing sensitive text and returning opaque file references. Before redaction: ```text Client Example Lantern Labs uses production-db.internal.example Contact avery@example.com about PROJECT-LANTERN-042. ``` Agent-visible result: ```text Client [ORG_a81f29d4a9c1e672540f68afc10d22c7] uses [DOMAIN_d12c88e1f730065c97d3f82f06d1188c] [ENTITY_6775c54c5116ff547754d1ac0ec5c577] [EMAIL_711ae704108cd6e952dcb27f0d6e999a] about [SENSITIVE_45f80ab22bc94e105a93aa830c7d3b9c]. ``` The placeholder values above are illustrative. Real values are deterministic for one local vault salt and will differ. This is the default `strict` mode, which also redacts capitalized words and acronyms that are not on the allow list, such as `Contact` here. `--mode balanced` skips those two passes and leaves `Contact` as it is. ## How It Works The agent never opens the private folder itself. It calls `redctx_*` tools, the server reads the raw files or configured GitHub issues, redacts every content field at one boundary, and returns only redacted text with opaque references such as `@p_1a2b3c4d5e6f`. In the diagrams, blue is the agent side, purple is processing inside redctx, amber is a check, green is redacted output or success, red is raw private data or a refusal, orange is a human step, explicit opt-in, or softer guardrail, and grey is a non-sensitive store. *This diagram is shown in the [README on GitHub](https://github.com/zoltan0803/redacted-context-mcp#readme).* Placeholders and path ids are deterministic for one vault salt, so the agent can follow the same name or file across calls. Only the local operator can turn them back into raw tex…