GDPR Compliance for AI Systems MCP Server
The server provides GDPR compliance automation for AI systems, covering DPIA, lawful basis, data subject rights, breach notification, and EU AI Act mapping.
Classify processing activities — determine applicable GDPR articles, DPIA requirement, special category status, and automated decision-making obligations.
Assess lawful basis — evaluate GDPR Article 6 bases and get a recommendation with rationale, including AI-specific considerations.
Generate DPIAs — create structured Data Protection Impact Assessments (Article 35) with risk evaluation and mitigation measures.
Handle data subject rights requests — get step-by-step guidance for access, rectification, erasure, restriction, portability, objection, and automated decision-making requests.
Assess breach notifications — evaluate breach severity, determine notification requirements under Articles 33–34 (72-hour rule), and generate notification content.
Map GDPR to EU AI Act — see where GDPR requirements align with EU AI Act obligations, useful for dual compliance.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@GDPR Compliance for AI Systems MCP Server generate a DPIA for our customer churn prediction model"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Verification is free and public: signed measurement cards and live verification at https://councilof.ai — measurement, not certification.
Gdpr Compliance Ai MCP
GDPR compliance MCP — DPIA automation, Article 30 records, Article 22 automated decision-making a...
GDPR compliance MCP — DPIA automation, Article 30 records, Article 22 automated decision-making audit, data subject request workflow.
🚀 Quick Start
# Install via pip
pip install gdpr_compliance_ai_mcp
# Or install via Smithery
npx -y @smithery/cli@latest install gdpr-compliance-ai-mcp --client claudeRelated MCP server: conformite-ia-mcp
⚡ Pay-per-call (PAYG) — no subscription
This MCP supports universal pay-per-call billing across the MEOK compliance fleet:
# One-time setup
export MEOK_PAYG_KEY="your_topup_token"
# Every tool call now deducts £0.05 from your balance.
# When balance hits zero, the tool returns a top-up URL.
# Works across all 7 MEOK compliance MCPs with the same token.No subscription — top up once, deduct per call.
£0.05/call default (configurable via
MEOK_PAYG_RATE_GBP).USDC on Base L2 accepted — set
MEOK_X402_RECEIVERand pay via stablecoin.Backward-compatible — when
MEOK_PAYG_KEYis unset, behaviour is unchanged.
Get a token: councilof.ai/payg (£10 / £50 / £200 top-up tiers).
✨ Features
GDPR Chapter V compliance
Cross-region data guard
Data localization
Transfer mechanism validation
Breach detection
📖 Documentation
🛡️ Compliance
This MCP server is built with EU AI Act compliance built-in:
✅ Article 9 — Risk Management System
✅ Article 13 — Transparency & Instructions for Use
✅ Article 15 — Bias Detection & Testing
✅ Article 26 — FRIA Support (where applicable)
✅ Article 50 — AI Content Watermarking (where applicable)
Need help getting compliant? Book a free 15-min diagnostic →
🏢 Enterprise
Need custom development, SLA guarantees, or white-label deployment?
View Pricing → | Contact Sales →
🤝 Part of the MEOK Ecosystem
This server is part of the Council of AI ecosystem — 26 PyPI packages · ~public measurement tools.
Domain | Purpose |
EU AI Act compliance marketplace | |
AI safety & monitoring | |
Sovereign AI platform | |
Legacy modernization |
📜 License
MIT © CSOAI-ORG
Configuration
Add to your claude_desktop_config.json (Claude Desktop) or your MCP client config:
{
"mcpServers": {
"gdpr-compliance-ai-mcp": {
"command": "uvx",
"args": ["gdpr-compliance-ai-mcp"]
}
}
}Or: pip install gdpr-compliance-ai-mcp then run the gdpr-compliance-ai-mcp command (stdio transport).
Examples
Once configured, ask your assistant, for example:
"Use
classify_processingto …""Use
lawful_basis_assessmentto …""Use
dpia_generatorto …"
Available Tools
6 toolsbreach_notificationA
Assess breach severity and notification requirements under GDPR Articles 33-34 (72-hour rule). Determines whether supervisory authority and data subject notification is required, and generates the notification content.
Args:
breach_description: Description of the personal data breach
data_categories_affected: Types of personal data affected
number_of_records: Approximate number of records/individuals affected
breach_type: Type of breach: "confidentiality" (unauthorized access), "integrity" (unauthorized alteration), "availability" (unauthorized loss of access)
detection_timestamp: When the breach was detected (ISO format, or "now")
ai_system_involved: Whether an AI system was involved in the breach
caller: Caller identifier for rate limiting
tier: Access tier (free/pro)
Inputs: breach_description (required), data_categories_affected (required), number_of_records, breach_type, +5 more. Returns: result
classify_processingA
Classify data processing activities per GDPR articles. Determines which GDPR articles apply, whether a DPIA is required, special category processing status, and automated decision-making obligations.
Args:
processing_description: Description of the data processing activity
data_categories: Types of personal data processed (e.g. ["name", "email", "biometric", "health"])
data_subjects: Categories of data subjects (e.g. ["employees", "customers", "children"])
processing_purposes: Purposes of processing (e.g. ["fraud detection", "personalization"])
automated_decision_making: Whether processing involves automated decisions affecting individuals
large_scale: Whether processing is conducted on a large scale
caller: Caller identifier for rate limiting
tier: Access tier (free/pro)
Inputs: processing_description (required), data_categories (required), data_subjects (required), processing_purposes (required),… Returns: result
crosswalk_to_eu_ai_actA
Map GDPR requirements to EU AI Act obligations. Shows where GDPR compliance satisfies, complements, or creates tension with EU AI Act requirements. Essential for organizations deploying AI in the EU that must comply with both regulations simultaneously.
Args:
gdpr_articles: Specific GDPR articles to map (or all if omitted)
focus_area: Focus on "all", "transparency", "automated_decisions", "data_governance", or "risk"
caller: Caller identifier for rate limiting
tier: Access tier (free/pro)
Inputs: gdpr_articles, focus_area, caller, tier, +1 more. Returns: result
dpia_generatorA
Generate a Data Protection Impact Assessment per GDPR Article 35. Produces a structured DPIA with necessity assessment, risk evaluation, and mitigation measures. Required before high-risk AI processing begins.
Args:
system_name: Name of the AI system or processing operation
system_description: Detailed description of the system and its processing
processing_purposes: Specific purposes of the processing
data_categories: Types of personal data processed
data_subjects: Categories of data subjects
data_volume: Approximate volume (e.g., "10,000 records", "1M users")
retention_period: How long data is retained (e.g., "2 years", "model lifetime")
third_party_sharing: Whether data is shared with third parties
international_transfers: Whether data is transferred outside the EEA
caller: Caller identifier for rate limiting
tier: Access tier (free/pro)
Inputs: system_name (required), system_description (required), processing_purposes (required), data_categories (required), +8 mor… Returns: result
lawful_basis_assessmentA
Determine the appropriate lawful basis for processing under GDPR Article 6. Evaluates all 6 lawful bases with AI-specific considerations and recommends the most appropriate basis with supporting rationale.
Args:
processing_purpose: The specific purpose of data processing
data_categories: Types of personal data involved
controller_type: "private" (company), "public" (government/public body)
relationship_with_data_subject: Nature of relationship (customer/employee/patient/citizen/visitor)
ai_processing: Whether an AI/ML system is used in processing
caller: Caller identifier for rate limiting
tier: Access tier (free/pro)
Inputs: processing_purpose (required), data_categories (required), controller_type, relationship_with_data_subject, +4 more. Returns: result
rights_request_handlerA
Handle data subject rights requests under GDPR Articles 15-22. Provides step-by-step guidance for responding to access, rectification, erasure, restriction, portability, objection, and automated decision-making requests with AI-specific considerations.
Args:
right_invoked: Which right is being exercised: "access", "rectification", "erasure", "restriction", "portability", "objection", "automated_decision"
data_subject_description: Description of the requesting data subject
processing_context: Context of the data processing involved
ai_system_involved: Whether an AI system processed the data subject's data
request_details: Specific details of the request
caller: Caller identifier for rate limiting
tier: Access tier (free/pro)
Inputs: right_invoked (required), data_subject_description (required), processing_context (required), ai_system_involved, +4 more. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool addresses a distinct GDPR compliance area (breach notification, processing classification, lawful basis, DPIA, rights requests, and EU AI Act mapping) with no overlap in purpose or functionality.
All tool names follow a consistent descriptive_pattern (noun_verb or adjective_noun) using snake_case, e.g., breach_notification, classify_processing, dpia_generator.
With 6 tools, the server covers the essential GDPR compliance tasks for AI systems without being too sparse or overly numerous. The count feels well-scoped for the domain.
The tool set covers major AI-relevant GDPR areas (DPIA, lawful basis, rights, breach, and crosswalk to AI Act). Minor gaps exist, such as tools for consent management or records of processing activities, but these are less critical for the stated purpose.
Maintenance
Related MCP Connectors
EU AI Act and GDPR checks with sources: classify an AI system, trace each duty, find the supervisor.
GDPR & privacy compliance: records of processing, data breaches, DSRs, risks, audits, AI systems.
Deterministic, sourced EU compliance checks: NIS2, DORA, GDPR, Cyber Resilience Act and AI Act.
AI inventory and EU AI Act compliance. Find AI tools and use cases, check new AI uses before launch.
Related MCP Servers
- AlicenseAqualityDmaintenanceProvides automated EU AI Act compliance tools, including risk classification, role determination, transparency disclosures, content watermarking, deepfake labeling, and security threat detection.1633Apache 2.0
- FlicenseNot gradedqualityDmaintenanceProvides an AI agent with regulatory compliance tools for the French/European market based on the AI Act and GDPR, including system classification, obligation listing, deadline schedules, legal reference lookup, and GDPR crosschecks.-
- AlicenseNot gradedqualityDmaintenanceEnables EU AI Act compliance for AI agent systems by providing risk classification, audit trails, gap analysis, and evidence package generation.51 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI impact assessments according to ISO/IEC 42005:2025, with built-in EU AI Act compliance and support for phases, categories, and assessment operations.MIT