Meok Governance Engine Mcp
Wire MEOK’s governance engine into Claude Code or Cursor so agent workflows enforce policies before tools run in production-facing builds.
Overview
MEOK governance engine MCP is a Ship-phase MCP server that connects coding agents to MEOK AI Labs governance controls over stdio.
What is this MCP server?
- Stdio MCP server (PyPI package meok-governance-engine-mcp v1.0.7) for local agent integration
- MEOK AI Labs governance layer meant to sit alongside other MEOK security MCPs
- Python transport via modelcontextprotocol stdio for Claude Desktop–style configs
- GitHub source at CSOAI-ORG/meok-governance-engine-mcp for self-hosted installs
- Complements injection-scan and test MCPs in a MEOK security toolchain
- Published version 1.0.7 on PyPI identifier meok-governance-engine-mcp
- Transport type stdio per MCP server schema
- Repository github.com/CSOAI-ORG/meok-governance-engine-mcp
What problem does it solve?
Agent workflows can call tools and change code faster than informal “don’t do X” rules can keep up, leaving solo builders without enforceable policy at the MCP layer.
Who is it for?
Indie builders running Python-based MCP stacks who want a MEOK-branded governance hook next to other MEOK security servers.
Skip if: Teams that need turnkey EU regulatory filings, injection scanning, or automated test harnesses without additional MEOK or custom policy tooling.
What do I get? / Deliverables
After you add the server to your agent, governance checks can be invoked through MCP tools so risky automation is gated before it hits your repo or production paths.
- Registered stdio MCP server in your agent config
- Agent-callable governance tooling via MEOK governance engine
- Repeatable policy checks alongside other MEOK MCP security tools
Recommended MCP Servers
Journey fit
Governance and policy enforcement belong on the Ship shelf because solo builders adopt it when hardening agent behavior before release, not during initial ideation. Security is the canonical subphase for runtime and design-time guardrails on what agents may do, which matches a governance engine’s role.
How it compares
MCP governance integration, not a prompt-injection scanner or golden-file test runner.
Common Questions / FAQ
Who is meok-governance-engine-mcp for?
It is for solo builders and small teams using Claude Code, Cursor, or generic MCP clients who want MEOK AI Labs governance exposed as agent-callable tools.
When should I use meok-governance-engine-mcp?
Use it during Ship when you are locking down agent behavior—before or alongside production deploys—not when you are only sketching product ideas.
How do I add meok-governance-engine-mcp to my agent?
Install the PyPI package meok-governance-engine-mcp, configure stdio transport in your MCP client, and point the command at the published identifier for v1.0.7.