AI compliance obligations across EU AI Act, ISO 42001, Colorado AI Act, NIST, HIPAA, SOX, FTC
GovernMy.ai MCP server — query AI governance obligations from Claude Desktop, Cursor, or any MCP-compatible client.
Covers EU AI Act, ISO 42001, Colorado AI Act, NIST AI RMF, HIPAA (AI provisions), SOX (AI provisions), and FTC AI guidance.
This MCP server gives an AI assistant (like Claude) the ability to query GovernMy's rules engine directly while you're working. You can ask questions like:
...and get structured regulatory obligations back as part of the conversation.
Important: this tool returns obligations, not verdicts. It never tells you "you're compliant" or "you're not compliant" — those are determinations only a human reviewer can make. Every response includes a humanReviewRequired flag where applicable.
After installing + restarting, try one of these:
cannotBeAutoSatisfied across all frameworks."~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonmcpServers object:{
"mcpServers": {
"governmy": {
"command": "npx",
"args": ["-y", "@governmyai/mcp-server"],
"env": {
"GOVERNMY_API_KEY": "ooa_live_your_key_here"
}
}
}
}
list_frameworks tool.Add the server to your Cursor MCP settings (Settings → MCP Servers):
npx-y @governmyai/mcp-serverGOVERNMY_API_KEY=ooa_live_your_key_hereAny client that speaks stdio MCP can run this server. Set GOVERNMY_API_KEY in the client's env for the server process.
| Variable | Required | Default | Purpose |
|---|---|---|---|
GOVERNMY_API_KEY | yes | — | Your GovernMy.ai API key |
GOVERNMY_API_URL | no | https://api.governmy.ai | Override API base URL (for local dev) |
get_obligations — query obligations that apply to an AI system given context (risk tier, role, industry, etc.)classify_risk_tier — classify an AI system's EU AI Act risk tier (unacceptable / high / limited / minimal)list_frameworks — list the frameworks the engine covers with metadataget_rule — fetch the full payload for a single obligation by idget_evidence_requirements — fetch required evidence artifacts for a set of obligationsget_cross_references — fetch cross-framework mappings for an obligationEvery tool response includes a notAVerdict notice reminding the AI assistant that obligations are not compliance verdicts.
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @governmyai/mcp-serverMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-governmyai-mcp-server": {
"command": "npx",
"args": [
"-y",
"@governmyai/mcp-server"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@governmyai/mcp-servernpmio.github.governmyai/mcp-server works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.