Omitly MCP server

omitly-mcp

A Model Context Protocol server that exposes Omitly's local, verifiable PDF redaction to AI agents (Claude Code, Claude Desktop, and any other MCP client).

Repository scope and licence — please read before opening a PR.

This repository is source-available, not open source. See LICENSE:

the code is published so you can read exactly what runs on your machine before

you let it touch a confidential document. It is not licensed for reuse in other

projects.

It contains the MCP server and the compiled wasm detection bundle. The Omitly

redaction engine, the tamper-evidence seal and the licensing implementation are

not in this repository and are developed privately; this code calls the

engine, it does not contain it.

Development happens in a private repository and is mirrored here on release, so

pull requests cannot be merged. Issues and security reports are very welcome

— see SECURITY.md.

The point of difference: an agent can redact a document without uploading it anywhere. Redaction runs on-device through the Omitly engine and returns a signed audit log proving the data was removed — the opposite of pasting a confidential file into a chat model.

Five of the eleven tools (findsensitiveregions, locatetext, checkredaction, verifyredaction, extractpdftext) work out of the box — npm install, no Rust toolchain, no native binary, no desktop app. They run on a wasm-bindgen build of the same detector that powers the web leak-checker at omitly.app, bundled directly in this package. createpdf, the two write tools (redactpdf, redactbyentity), and the two seal-verification tools (verifyseal, verify_document) still need a configured native engine — see "Build & run" below. Neither seal tool has a wasm fallback yet: there is no wasm seal-verification path (tracked in issue #113), so both always require the native engine, even though checking a seal needs no licence.

Tools

Shortened. The full README is on GitHub.