Engineered GDPR compliance for engineers and AI agents: pull rules, implement, submit evidence.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Engineered Compliance Infrastructure for engineers and AI agents.
RuleMesh delivers source-traced rules for GDPR and the EU AI Act: determine applicability, retrieve the requirements and implementation checklists that apply to a system, submit evidence signals, and track human verification. It runs as a hosted remote MCP server at https://api.rulemesh.com/mcp (Streamable HTTP, OAuth login), consumable from any MCP client.
This repo is the canonical home for the server's listing (server.json, published to the MCP Registry as com.rulemesh/compliance) and client setup docs.
You authenticate once in the browser (email/password or Google); no API key to manage. A RuleMesh account is required. The FREE tier includes GDPR. EU AI Act access and control mappings are available with a paid subscription.
Add to ~/.codex/config.toml:
Then codex mcp login rulemesh (opens the browser for OAuth), and /mcp in the TUI to confirm the tools loaded.
Run /mcp and follow the browser login. A packaged plugin is also available at RuleMesh/rulemesh-claude-plugin.
Add a remote (Streamable HTTP) MCP server pointing at https://api.rulemesh.com/mcp. For example, Claude Desktop (claude_desktop_config.json) or Cursor (.cursor/mcp.json):
The server groups its 19 tools around one loop: plan, pull, implement, prove. GDPR and the EU AI Act are live today, with access depending on the account's plan.
list_regulations, list_frameworks, lookup_definition, get_compliance_plan, scope_next_question, scope_classify, scope_retrieve_source, scope_query_applicable, scope_update_profilepull_rules, scan_compliancesubmit_signals, submit_signals_batchget_progress, get_ticket_status, get_scan_sessions, start_scan, end_scan, resume_sessionFour prompts package the common workflows: implement_bundle, scan_and_report_bundle, review_bundle, and plan_compliance. One resource, regulation://{id}, returns regulation metadata.
Your coding agent reads your repository locally using RuleMesh requirements. RuleMesh does not read or receive source-code contents. Evidence submissions contain the evidence description and relevant filenames; they do not certify compliance or mark a requirement verified. Verification remains a human action.
OAuth 2.1 with PKCE and Dynamic Client Registration. Clients register themselves and open a browser login; tokens refresh automatically.
RuleMesh is Engineered Compliance Infrastructure β the engineered rule graph that sits between regulation as written and software as built, consumable by engineers, AI agents, and auditors. It defines what each obligation requires, how to execute it with framework-specific controls, and what evidence proves it was done. GDPR and the EU AI Act are released today; more regulations are on the roadmap. β rulemesh.com
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/compliance)<a href="https://allmcps.com/mcp/compliance"><img src="https://allmcps.com/api/badge/compliance?style=directory" alt="Compliance on AllMCPs" /></a>