{
  "uid": "cogitave.learn.native-mcp-interface",
  "kind": "module",
  "href": "/modules/native-mcp-interface/",
  "title": "The native MCP interface to Core",
  "summary": "Read Core's MCP interface as the source of truth for how an agent queries the estate - why the surface is native rather than adapted, the protocol contract it commits to, and the tools and resources you call.",
  "type": null,
  "products": [
    "cogitave-core"
  ],
  "roles": [
    "developer"
  ],
  "levels": [
    "intermediate"
  ],
  "subjects": [
    "software-engineering"
  ],
  "headings": [],
  "source": "By the end of this module, you'll be able to:\n- Explain why MCP is Core's canonical query surface rather than an adapter bolted onto REST, per ADR-0003.\n- State the protocol baseline Core's MCP server commits to: spec revision, transports, schema dialect, and how tool errors are reported.\n- Name Core's MCP tools and resources, what each returns, and how `query_graph` is bounded so it cannot become a general escape hatch.\n- Distinguish the read tools from the propose-only request-lifecycle tools, and explain why writes never mutate protected state directly.\n",
  "units": [
    "cogitave.learn.native-mcp-interface.introduction",
    "cogitave.learn.native-mcp-interface.the-mcp-surface",
    "cogitave.learn.native-mcp-interface.tools-and-resources",
    "cogitave.learn.native-mcp-interface.knowledge-check",
    "cogitave.learn.native-mcp-interface.summary"
  ],
  "durationInMinutes": 25,
  "badge": "cogitave.learn.native-mcp-interface.badge",
  "partOf": "cogitave.learn.paths.build-on-core"
}