DPO2U MCP Platform Server

How to use

Start by launching the local MCP server and connect your client (Claude Desktop or your own tooling) to access the 17 tools for compliance automation. You will run the local server, then use the provided MCP CLI or HTTP API to execute tools like auditinfrastructure, assessrisk, and generateprivacypolicy. The system is designed for fully localized processing with cryptographic safeguards, while exposing a curated set of tools for governance, risk, and privacy.

How to install

# Step 1: Install prerequisites (Node.js and npm)
# Ensure Node.js 14+ and npm are available on your system
```

```
# Step 2: Clone the project repository
cd /opt
git clone https://github.com/dpo2u/dpo2u-mcp.git
```

```
# Step 3: Install dependencies
cd /opt/dpo2u-mcp
npm install
```

```
# Step 4: Prepare environment variables
cat > .env << EOF
LEANN_API_URL=http://localhost:3001
LEANN_API_KEY=leann-api-2025
OLLAMA_API_URL=http://172.18.0.1:11434
OPENFHE_SCRIPTS_PATH=/opt/openfhe/scripts
OPENFHE_TEMP_DIR=/tmp/openfhe
PYTHON_PATH=python3
EOF
```

```
# Step 5: Build the TypeScript project
npm run build
```

```
# Step 6: Run the local MCP server
node dist/index.js
```

```
# Step 7: (Optional) Use the HTTP API for tooling from a client
npm run start:http
```

```
# Step 8: Configure the Claude Desktop integration (example)
# Add a config entry pointing to the local server binary
# The following config runs the MCP server via Node and passes environment variables

Additional configuration and usage notes

You can customize onboarding and automation behavior via environment variables and CLI options. For automated onboarding in non-interactive environments, you can enable quick onboarding and set company details as shown in the examples. Secrets should be supplied through environment variables or a secrets file as described in the secret management notes.

Security and privacy considerations

All processing is designed to be 100% local by default, with cryptographic protections for data in transit and at rest. Logs are auditable, and the system is built to comply with LGPD/GDPR by design.

Usage examples

Use the MCP CLI to list tools, call a specific tool with arguments, or reset onboarding. For example, list available tools, then execute a tool like auditinfrastructure with a target and depth that fits your environment.

auditinfrastructure

Audits your infrastructure to assess compliance status and identify gaps.

checkcompliance

Performs a detailed verification of compliance against LGPD/GDPR requirements.

assessrisk

Evaluates risks with DPIA/RIPD and produces actionable remediation steps.

mapdataflow

Visualizes data flows to help you understand processing and data movement.

generateprivacypolicy

Generates customized privacy policies tailored to your operations.

createdporeport

Provides executive DPO reports summarizing compliance posture.

analyzecontract

Analyzes contracts and DPAs for data protection clauses.

simulatebreach

Simulates data breach scenarios to test response capabilities.

verifyconsent

Audits consent mechanisms for validity and completeness.

calculateprivacyscore

Calculates a privacy maturity score across controls.

encryptedreporting

Produces reports with data encrypted at rest and in transit.

privatebenchmark

Performs cross-organization benchmarks without exposing metrics.

zkcomplianceproof

Generates zero-knowledge proofs of regulatory compliance.

fheexecutivedashboard

Executive KPI dashboard with encrypted data.

homomorphicanalytics

Analytics over encrypted data preserving privacy.

securedatasharing

Secure multi-party data sharing without exposing underlying data.