Bring your documents to Chat

The Omissis MCP server allows Claude to search, read, and analyze your pseudonymized PDF documents — with privacy guaranteed by design.

Key Features

Search documents

Find files by name or folder path in your personal and shared drives.

Read content

Extract and analyze the full pseudonymized text of any processed document.

Email reports

Generate stylized Word reports with real de-pseudonymized data, sent securely to your email.

Use cases

Here are some example prompts you can use in Claude

Search for a Document

“Find the contract signed with Rossi last month.” — Claude searches your drives and returns the corresponding files in pseudonymized form.

Summarize a document

“Summarize the medical report I uploaded to Omissis.” — Claude reads the pseudonymized content and produces a structured summary.

Generate and send a report

“Send me a Word report of all Q1 contracts.” — Claude composes the stylized document, restores the real data on the server side, and sends it to you via email.

Browse a folder

“List all documents in the Legal/Contracts folder.” — Claude filters your drives by path and returns the corresponding files.

Cross-sectional analysis

“Compare the two NDAs in the Acme Corp shared drive.” — Claude reads both documents and produces a comparative analysis, all in pseudonymized form.

Available tools

Here is what our MCP service provides

search_files

Search for documents processed by Omissis. Filter by file name fragment and/or folder path. Returns file metadata and an opaque document_id used by other tools.

get_file_content

Reads the full pseudonymized text of a document. Requires the document_id returned by search_files. Supports PDF, plain text, and other processed formats.

send_file_for_depseudonymization

De-pseudonymizes the content and sends the result via email to the authenticated user. Real entity values are restored server-side and are never shown in conversation. Supports DOCX, XLSX, TXT, and Markdown output formats.

How Does It Work?

Omissis MCP uses OAuth 2.0 with PKCE. When you connect Omissis to Claude, you will be redirected to the Omissis authorization page where you will approve access with your existing account. No separate API key is required.

MCP Server URL

				
					https://mcp.edito-pdf.com

Client ID (OAuth)

				
					claude

OAuth Endpoint (auto-discovery)

Endpoint	Method	URL
Discovery	GET	`…/mcp/.well-known/oauth-authorization-server`
Authorization	GET / POST	`…/mcp/authorize`
Token exchange	POST	`…/mcp/token`
Token revocation	POST	`…/mcp/revoke`
MCP (Streamable HTTP)	POST	`…/mcp`

Connect via WebUI

Open Claude Desktop and go to Settings → Connectors
Click “+” then “Add custom connector”
Paste the MCP server URL shown above
On the authentication page, log in with your Edito-Pdf credentials
The Edito-Pdf connector will appear in the list of your active connectors

Connect via Claude Desktop (manual JSON)

If you need to configure Claude Desktop manually, add the following snippet to your claude_desktop_config.json file:

				
					{
  "mcpServers": {
    "omissis": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.edito-pdf.com",
        "--static-oauth-client-info",
        "{\"client_id\":\"claude\"}"
      ]
    }
  }
}

Configuration file location:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

After modifying the file, restart Claude Desktop.

Requirements and availability

A paid Omissis account on app.edito-pdf.com.
At least one document uploaded and processed (pseudonymized) on Omissis.
No geographical restrictions — available worldwide.
No administrator or developer account required.

GDPR Compliant

All data is processed on European infrastructure. Sensitive personal data is never transmitted to the AI provider.

Privacy and data management

The server only accesses documents explicitly requested by the user, which are anonymized and pseudonymized.
No data is stored by the MCP server beyond the duration of the individual request.
All communications are encrypted via HTTPS/TLS.
De-pseudonymization (restoration of real entities) occurs exclusively server-side and is delivered via email — real values are never included in MCP responses nor are they visible in chat.
Consult our full Privacy Policy.