Ask your AI assistant. It answers from the Body of Knowledge.

A public Model Context Protocol server gives Claude, and any other MCP client, direct access to this site: the obligation register, the crosswalk, the glossary, the patterns and the templates. Every answer names the page it was read from. No account, no key, nothing stored.

Your question “What applies to a deployer of a high-risk system before December 2027?”
MCP client Claude, Claude Code, Cursor, VS Code or an agent you build
The MCP server 12 read-only tools; no account, no key, nothing stored
Open data API 182 obligations, 33 patterns, 328 glossary terms, the same data as these pages
Sourced answer The canonical page, its dataset, BoK v0.5.0, CC BY 4.0

From your question to the source The server holds nothing of its own: it reads the open data API behind these pages, so every answer names the page it was read from.

The endpoint

Live since 2026-09-25. Streamable HTTP, read-only, no authentication. Clients that discover servers read its server card (JSON).

https://mcp.aigovernanceengineer.com/mcp

Connect it in a minute

Claude (web and desktop)

On Pro and Max plans open Customize > Connectors, choose Add custom connector, paste the endpoint above and leave the OAuth fields empty. On Team and Enterprise plans an owner adds it once under Organization settings > Connectors; members then switch it on from Customize > Connectors.

Claude Code

claude mcp add --transport http aige https://mcp.aigovernanceengineer.com/mcp

Add --scope project to share it with your team through .mcp.json.

Any other MCP client (Cursor, VS Code, agents you build)

{
  "mcpServers": {
    "aige": { "type": "http", "url": "https://mcp.aigovernanceengineer.com/mcp" }
  }
}

What it answers

Twelve read-only tools over 182 obligations, 33 patterns and 328 glossary terms, plus the crosswalk, the templates, the open control profiles and the full text of the book.

Tool	What it returns	Try asking
`search_bok`	Chapters, sections and pattern pages that match a question, best first, each with its anchor URL.	“Where does the book explain the Art. 6(3) filter?”
`get_obligations`	Rows of the obligation register filtered by framework, role, system class, status, layer or date.	“What applies to a deployer of a high-risk system before December 2027?”
`get_obligation`	One obligation by its stable id, with milestones, patterns and crosswalk references.	“Show me AIGE-OBL-EUAIA-ART9 and the evidence it expects.”
`map_clause`	The clauses of other frameworks that sit on the same topic as a given clause.	“What does ISO/IEC 42001 say where the AI Act has Art. 9?”
`search_glossary`	Glossary terms whose name or definition match, each with its term page.	“Define deployer and contrast it with provider.”
`get_term`	One term: definition, source, the chapters that use it and related terms.	“What is a serious incident under the AI Act?”
`list_patterns`	The engineering patterns, optionally for one stack layer.	“Which patterns live in the runtime layer?”
`get_pattern`	One pattern in full: problem, solution, consequences and what it maps to.	“Walk me through the Kill Switch pattern.”
`list_controls`	The reference controls of the open control profiles, filtered by profile, layer, status, depth or words.	“Which evaluation environment controls are specified in full?”
`get_control`	One draft control specification: objective, failure modes, verification, evidence, mappings and sources.	“Show me AIGE-CTL-EVAL-002 and how a third party verifies it.”
`list_templates`	The library of JSON Schemas, filled examples and human templates.	“Which templates exist for impact assessments?”
`get_template`	One template or schema with the content of its files.	“Give me the incident record schema and an example.”

What you can rely on

Sourced answers. Every answer carries the canonical page to cite, the dataset it came from, the Body of Knowledge version (v0.5.0) and the CC BY 4.0 licence.
Same data as the site. The server holds nothing of its own: it reads the open data API, so it is never ahead of or behind these pages.
Private by design. No account, no key, no conversation stored; request logs keep no client address.
Open source. The code, its tests and a guide to run it yourself are in tools/mcp-server.