Mcp Server
Wire your coding agent into GovernMy.ai so obligation lookups cover EU AI Act, ISO 42001, Colorado AI Act, NIST, HIPAA, SOX, and FTC while you design or ship AI features.
Overview
io.github.governmyai/mcp-server is a MCP server for the Ship phase that queries GovernMy.ai for AI compliance obligations across EU AI Act, ISO 42001, Colorado AI Act, NIST, HIPAA, SOX, and FTC.
What is this MCP server?
- Surfaces AI compliance obligations across EU AI Act, ISO 42001, Colorado AI Act, NIST, HIPAA, SOX, and FTC from one MCP
- Stdio npm package @governmyai/mcp-server v0.1.4 for Claude Code, Cursor, and other MCP hosts
- Requires GOVERNMY_API_KEY with optional GOVERNMY_API_URL override defaulting to https://api.governmy.ai
- Governed API workflow: register a free developer key at https://governmy.ai/developers before first tool call
- MCP integration layer—not a local checklist skill—so answers stay tied to GovernMy’s maintained obligation corpus
- Server version 0.1.4 on npm as @governmyai/mcp-server with stdio transport
- Covers obligation themes for EU AI Act, ISO 42001, Colorado AI Act, NIST, HIPAA, SOX, and FTC
- One required secret: GOVERNMY_API_KEY; default API base https://api.governmy.ai
What problem does it solve?
Indie builders cannot keep seven-plus AI and enterprise compliance regimes straight while coding features in the agent sidebar.
Who is it for?
Solo founders shipping AI-assisted products who need repeatable obligation lookups from Claude Code or Cursor before launch.
Skip if: Teams that want offline-only compliance with no API key or those needing certified legal sign-off instead of developer-oriented guidance.
What do I get? / Deliverables
After you register GOVERNMY_API_KEY and add the stdio server, your agent can pull framework-aligned obligation context into planning and pre-launch security reviews.
- Agent-callable compliance obligation lookups across named AI and enterprise frameworks
- Repeatable pre-launch governance Q&A inside your coding session
- Documented API integration pattern with optional GOVERNMY_API_URL override
Recommended MCP Servers
Journey fit
Compliance mapping belongs on the Ship shelf because founders must lock governance and legal exposure before launch, not after users are on production traffic. Security is the canonical subphase for regulatory and control-framework checks that gate what you can safely release.
How it compares
Hosted compliance MCP integration, not a static markdown policy skill or generic web-search plugin.
Common Questions / FAQ
Who is io.github.governmyai/mcp-server for?
It is for indie and solo builders using MCP-enabled agents who must reason about EU AI Act, ISO 42001, Colorado AI Act, NIST, HIPAA, SOX, or FTC while building AI features.
When should I use io.github.governmyai/mcp-server?
Use it during Ship security reviews, architecture decisions, and launch prep whenever you need GovernMy.ai obligation context inside the agent instead of tab-hopping.
How do I add io.github.governmyai/mcp-server to my agent?
Get a free GOVERNMY_API_KEY at https://governmy.ai/developers, install @governmyai/mcp-server v0.1.4 over stdio, set the secret env var, and register the server in your MCP client config.