{
  "uid": "cogitave.learn.native-mcp-interface.introduction",
  "kind": "moduleUnit",
  "href": "/modules/native-mcp-interface/introduction/",
  "title": "Introduction",
  "summary": "",
  "type": null,
  "products": [],
  "roles": [],
  "levels": [],
  "subjects": [],
  "headings": [
    "What you will get from this module",
    "Where this fits"
  ],
  "source": "Cogitave Core is one canonical model of the whole estate: a property graph that\nevery product, standard, and agent shares. Earlier modules in this path build\nand query that graph. This module is about the surface an agent actually calls\nto reach it: the **native MCP interface**.\n\n\"Native\" is a specific claim, not a decoration. [ADR-0003](../../../../core/docs/decisions/0003-mcp-native.md)\nrecords the decision in plain terms: Core's tools and resources over the Model\nContext Protocol are the **canonical** query surface, and REST, GraphQL, and\n`llms.txt` are generated conveniences over the identical catalog, graph, and\nsearch materializations - not the other way around. A human's UI and an agent\ncall the same tool, against the same schema, and get the same answer.\n\nConcretely, Core embeds an MCP server directly in its Rust hot path, targeting\n**spec revision 2025-11-25**, reachable over stdio for local agents (the namzu\nkernel, CI) or Streamable HTTP for edge and remote callers. Every tool's input\nand output validate against **JSON Schema 2020-12** - the same dialect the\nproperty graph's own schema uses, so a tool's structured result and the graph\nmodel agree by construction rather than by convention.\n\nEverything in this module is grounded in what\n[mcp-interface.md](../../../../core/docs/mcp-interface.md) and ADR-0003 actually\nstate today. Read this module the way you would read those documents: as the\nsource of truth, with this module teaching you to use them rather than\nparaphrasing them from memory.\n\n## What you will get from this module\n\nBy the end, you will be able to reason about a call to Core over MCP end to\nend: why the surface is native rather than adapted, what protocol guarantees\nyou can rely on - transports, schema dialect, the error model - which tools and\nresources exist and what each one returns, and where the governance tools stop\nat \"propose\" instead of \"mutate.\"\n\n## Where this fits\n\nThis is module 3 of *Build on Cogitave Core*. It assumes you can already picture\nCore as a property graph and does not re-teach that model; if a term here is\nunfamiliar, [mcp-interface.md](../../../../core/docs/mcp-interface.md) links\nonward to the substrate and query docs it builds on.\n",
  "partOf": "cogitave.learn.native-mcp-interface",
  "durationInMinutes": 4,
  "quiz": null
}