{
  "uid": "cogitave.learn.native-mcp-interface.summary",
  "kind": "moduleUnit",
  "href": "/modules/native-mcp-interface/summary/",
  "title": "Summary",
  "summary": "",
  "type": null,
  "products": [],
  "roles": [],
  "levels": [],
  "subjects": [],
  "headings": [
    "Next steps"
  ],
  "source": "You now know Core's native MCP interface well enough to reason about a call to\nit, not just recite that one exists.\n\nIn this module, you:\n\n- Learned why MCP is Core's **canonical** query surface rather than an adapter:\n  ADR-0003 chose tools/resources over MCP as the source of truth, with REST,\n  GraphQL, and `llms.txt` generated from the identical catalog, graph, and\n  search materializations, so humans and agents cannot drift onto different\n  data.\n- Pinned the **protocol baseline**: spec revision 2025-11-25, stdio and\n  Streamable HTTP transports, JSON-RPC 2.0 over a stateful session, JSON Schema\n  2020-12 for every tool's input and output, and tool input-validation failures\n  returned as tool execution errors so a calling model can self-correct.\n- Named Core's **tools and resources** - `docs_search` through\n  `describe_schema`, the `cogitave://{type}/{id}` resource template with\n  `subscribe` and change notifications - and saw how `query_graph` is bounded\n  (read-only, allowlisted labels, capped depth, capped rows) so it cannot become\n  a general escape hatch.\n- Distinguished the **open reads** from the **propose-only writes**:\n  `request_intake` and `advance_stage` stage a draft node and open a GitHub\n  issue/PR, and never mutate protected state directly.\n\n## Next steps\n\n- The **mcp-interface.md** doc, in the estate's core repository, is worth a\n  re-read with this module's context - it is short, and now every section\n  should be legible on its own.\n- **ADR-0003** is the estate's decision record itself; revisit it if you\n  want the full trade-off behind \"native.\"\n- @cogitave.learn.paths.build-on-core - this module is part 3 of 4 in *Build on\n  Cogitave Core*; the path also covers the property-graph model itself, Cogitave\n  Query, and how products project their state into Core.\n",
  "partOf": "cogitave.learn.native-mcp-interface",
  "durationInMinutes": 3,
  "quiz": null
}