The Schematica Suite

CoreModels is the engine. The Suite is what it powers: the Schematica Library, the MCP server, the design plugins — and the wider ecosystem of standards they connect to.

Two words that are easy to confuse and deliberately kept apart. The Schematica Suite is the set of products CoreModels belongs to. The Schematica ecosystem is the wider world of standards, vocabularies and communities those products connect to. CoreModels is the engine of the first and a citizen of the second.

The Suite

CoreModels

The platform: one connected core model, governed by people, read by every agent. The Core Model →

Schematica Library

A curated, community-driven catalog of production-ready data models, ontologies, taxonomies and content structures across industry domains — healthcare, legal, e-commerce, web standards, enterprise. Browse, preview, and activate any model into CoreModels. library.schematica.io →

The MCP server

Open MCP access to the Library, so an assistant can discover what exists before it builds — and the CoreModels endpoint beside it, so it can read the definition of every item and field in a governed model. The MCP server →

The design plugins

SchemaFlow, RealContent and ContentFlow bring structured models into Figma and FigJam — content models built to SEO standards, live structured content in designs, and conversational flows sourced from data. schematica.io →

From discovery to execution

  1. 1

    Discover

    Browse the Schematica Library for a model that already fits — a FHIR profile, a schema.org product, an industry taxonomy — instead of starting from a blank page.

  2. 2

    Activate

    Import it into CoreModels, adapt it to your organization, extend it with your own definitions, and map it to the systems you actually run.

  3. 3

    Operationalize

    Expose the governed result through the API and the MCP endpoint, so pipelines, integration platforms and agents read authoritative definitions at runtime. Discovery becomes execution.

The ecosystem

CoreModels does not ask an organization to adopt a new standard. It reads and writes the ones already in play — JSON Schema, JSON-LD, ShEx, OWL, LinkML, Avro, Protocol Buffers, ODCS, the Open Semantic Interchange, MACH ODM, FHIR and schema.org among them — and holds the mappings between a standard and the schemas that conform to it. When a standard moves, the model tracks the move; when two standards describe the same thing differently, the model records both and the correspondence between them. Every format and platform, in the catalog →

Enterprise and Partner

Enterprise is one organization governing its own schemas: SSO, audit logs, an SLA, dedicated infrastructure, and an agreement procurement can sign. The Partner Program is a hub governing a shared core across independent units — a research consortium, a holding company, a federation of agencies — with a federated workspace architecture, schema propagation and drift control across units, and a discounted Enterprise license. Partner is applied for, not purchased. Plans, Enterprise and Partner →

The company

CoreModels® is a registered trademark.