odgs-mcp-server — Claude Code MCP server: data validation with S-Certs
Hooks an AI agent up to the ODGS engine: payloads get checked against governance rules, maturity gets scored, and signed S-Certs come back.
claude mcp add --env ODGS_PROJECT_ROOT=<ODGS_PROJECT_ROOT> --env ODGS_API_KEY=<ODGS_API_KEY> --transport stdio odgs-mcp-server -- uvx odgs-mcp-serverWhat odgs-mcp-server does
The server speaks stdio, so any MCP client can drive it. The free tier ships validate_payload, validate_batch, list_packs, governance_score and conformance_check. Each payload check returns a signed S-Cert, which is what makes the result auditable rather than just a log line.
The maturity score covers eight ISO/IEC 38505-1 and ISO/IEC 25012 pillars, from 0 to 100, with a per-pillar gap breakdown. Install the separate odgs-maturity package or the score falls back to a built-in heuristic.
Regulation compilation, semantic drift detection, conflict detection and rule harvesting from Databricks, Snowflake and Collibra sit behind a Certified Pack licence. Those tools read the key from ODGS_API_KEY. Point ODGS_PROJECT_ROOT at your project directory in the client config.
What it helps with
- check a data payload against governance rules and get a signed S-Cert
- score project governance maturity across eight ISO pillars and see the gaps
- validate several payloads together in one call
- run the ODGS conformance self-check at L1 or L2
- turn regulation text into valid ODGS rule JSON under a licence
Example prompts for the agent
- Run
validate_payloadon this dataset and show me the S-Cert - Score the project with
governance_scoreand break down the pillar gaps - Compile the regulation text into ODGS rules with
compile_regulation
How to install odgs-mcp-server
Platform CLI
claude mcp add --env ODGS_PROJECT_ROOT=<ODGS_PROJECT_ROOT> --env ODGS_API_KEY=<ODGS_API_KEY> --transport stdio odgs-mcp-server -- uvx odgs-mcp-serverReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from odgs-mcp-server <command>
Platform CLI
codex mcp add odgs-mcp-server --env ODGS_PROJECT_ROOT=<ODGS_PROJECT_ROOT> --env ODGS_API_KEY=<ODGS_API_KEY> -- uvx odgs-mcp-serverReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from odgs-mcp-server <command>
Config file
{
"mcpServers": {
"odgs-mcp-server": {
"command": "uvx",
"args": [
"odgs-mcp-server"
],
"env": {
"ODGS_PROJECT_ROOT": "<ODGS_PROJECT_ROOT>",
"ODGS_API_KEY": "<ODGS_API_KEY>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from odgs-mcp-server <command>
Config file
{
"servers": {
"odgs-mcp-server": {
"type": "stdio",
"command": "uvx",
"args": [
"odgs-mcp-server"
],
"env": {
"ODGS_PROJECT_ROOT": "<ODGS_PROJECT_ROOT>",
"ODGS_API_KEY": "<ODGS_API_KEY>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from odgs-mcp-server <command>
Platform CLI
gemini mcp add -e ODGS_PROJECT_ROOT=<ODGS_PROJECT_ROOT> -e ODGS_API_KEY=<ODGS_API_KEY> odgs-mcp-server uvx odgs-mcp-serverReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from odgs-mcp-server <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about odgs-mcp-server
How do I install odgs-mcp-server in Claude Code?
One command: claude mcp add odgs-mcp-server -e ODGS_API_KEY=<ODGS_API_KEY> -- uvx odgs-mcp-server. To pass a project path as well, run `claude mcp add --env ODGS_PROJECT_ROOT=<ODGS_PROJECT_ROOT> --env ODGS_API_KEY=<ODGS_API_KEY> --transport stdio odgs-mcp-server -- uvx odgs-mcp-server`.
What does odgs-mcp-server do?
It links an MCP agent to the ODGS engine for rule-based payload checks, maturity scoring and signed S-Cert issuance.
Do I need an API key to use it?
Validation, scoring and the conformance check run without one. Compilation, drift, conflicts and catalog sync need a Certified Pack licence plus ODGS_API_KEY.
