A remote MCP (Model Context Protocol) server providing AI agents with access to a comprehensive compliance knowledge graph containing **692+
A remote MCP (Model Context Protocol) server providing AI agents with access to a comprehensive compliance knowledge graph containing 692+ compliance frameworks, 14,200+ controls, and 819,000+ cross-framework mappings. The compliance mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 10 defined tools rather than through you.
Everything the assistant can do here goes through one of these:
agent_search_frameworks — Search and list compliance frameworks by name, keyword, or jurisdictionagent_get_framework — Get detailed information about a specific compliance frameworkagent_get_framework_controls — Get all controls for a compliance framework, optionally filtered by domainagent_get_control — Get detailed information about a specific control by codeagent_get_control_cross_references — Get cross-framework mappings for a control (equivalent controls in other frameworks)agent_cross_framework_map — Map controls between two compliance frameworksagent_coverage_report — Get cross-framework coverage analysis for a frameworkagent_search — Full-text search across controls and frameworksagent_platform_stats — Get platform statistics (framework, control, mapping counts)agent_pricing_info — Get API pricing tiers and current usage informationInstallation goes through your MCP client rather than a global install: point it at @theartofservice/compliance-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Compliance's toolset — agent_search_frameworks, agent_get_framework, agent_get_framework_controls and 7 more — is a fair guide to whether it matches your workflow. It is maintained by gjb65; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| agent_search_frameworks | Search and list compliance frameworks by name, keyword, or jurisdiction |
| agent_get_framework | Get detailed information about a specific compliance framework |
| agent_get_framework_controls | Get all controls for a compliance framework, optionally filtered by domain |
| agent_get_control | Get detailed information about a specific control by code |
| agent_get_control_cross_references | Get cross-framework mappings for a control (equivalent controls in other frameworks) |
| agent_cross_framework_map | Map controls between two compliance frameworks |
| agent_coverage_report | Get cross-framework coverage analysis for a framework |
| agent_search | Full-text search across controls and frameworks |
| agent_platform_stats | Get platform statistics (framework, control, mapping counts) |
| agent_pricing_info | Get API pricing tiers and current usage information |
{
"mcpServers": {
"compliance-intelligence": {
"url": "https://api.theartofservice.com/mcp",
"headers": {
"Authorization": "Bearer tas_YOUR_API_KEY"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.