# Coremodels MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.coremodels%2Fcoremodels
Registry id: `mcp-registry/io.coremodels/coremodels`
Status: live (checked 2026-11-22T19:30:35.978Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 822
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "coremodels-mcp-server": {
      "type": "http",
      "url": "https://go.coremodels.io/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http coremodels-mcp-server https://go.coremodels.io/mcp
```

## Tools (37)

- `analyze_concept_impact`: Answers 'what is affected if this concept changes?' for a governed type, element or controlled vocabulary. Returns: where it is used inside the model (blast rad
- `audit_vendor_project`: Audits vendor artifacts (e.g. a dbt manifest) against the governed CoreModels graph — read-only. Reports coverage (what is/isn't governed, canonical-mapping cov
- `check_admissible`: Check whether a relation would be admissible before writing it. Reads the SAME relation-group rule table create_relation and bulk_create validate against, so th
- `contact_sales`: Ask the CoreModels team for a scoping call: the escalation path when this MCP server cannot do the job alone (a plan limit, a missing capability, or a question 
- `core_models_get_mixins_info`: Get information about all mixins in a CoreModels project. Mixins define structured metadata used for mapping models, system integrations, and other extensions. 
- `core_models_get_relation_groups_info`: Get information about relation groups for a CoreModels project. Use the relation groups to create a relation between two nodes.
- `export_avro`: Export project data as an Avro (.avsc JSON) schema string.
- `export_json_ld`: Export project data in JSON-LD format using a configured export profile. Use `fetch_json_ld_import_profiles` first to discover the configTypeId. At least one of
- `export_jsonschema`: Export project data as a JSON Schema string.
- `export_linkml`: Export project data as a LinkML (YAML) schema string.
- `export_owl`: Export project schema as an OWL ontology (Turtle): owl:Class per Type, Datatype/ObjectProperty per Element with domain/range, rdfs:subClassOf inheritance, cardi
- `export_rml`: Export the project as an RML mapping document (RML-Core + RML-IO, namespace http://w3id.org/rml/): one rml:TriplesMap per Type, an rml:logicalSource per source 
- `export_shex`: Export project data as a ShEx (Shape Expressions) schema string.
- `export_sql`: Export the project's types as runnable SQL DDL (CREATE TABLE statements) for PostgreSQL / SQLite. Identifiers are double-quoted; column types come from the Json
- `fetch_json_ld_import_profiles`: Fetch JSON-LD import/export profiles available for a project (id and label each). Pass configTypeId to read that one profile's field mapping instead: every JSON
- `fetch_json_schema_import_profiles`: Fetch JSON Schema import/export profiles available for a project (id and label each). Pass configTypeId to read that one profile's field mapping instead: every 
- `generate_synapse_manifests`: Generate Synapse curation-manifest CSV templates from a schema — the tabular companion to the transform_schema synapse export. Two artifacts per type: {name}.ma
- `generate_vendor_artifacts`: Generates vendor artifacts from the governed CoreModels graph. For dbt: a schema.yml with enforced model contracts — column data types, not_null/unique constrai
- `get_job_status`: Get the status of a background job in a project, e.g. the copy started by copy_project or a background import_owl. Returns { jobDetailsId, projectId, type, stat
- `get_mixins_and_relation_groups`: Get the project schema: all mixin definitions and all relation-group definitions. Use this once at the start of a session to discover the IDs needed by other to
- `get_modeling_guide`: Returns the CoreModels modeling guide (markdown): how to import vs build, what each relation group means and which direction it runs (Domain Includes, Range Inc
- `get_project_summary`: Labels and IDs of types, elements, and taxonomies in the project. Each category is paginated independently. Pagination: - First call: omit page (defaults to 0).
- `get_vendor_integration_status`: Lists the registered vendor connectors (dbt, ...) with capabilities and expected artifacts, and — when 'vendor' is given — the project's last-import state for t
- `list_comments`: List the discussion (comments and replies) of a CoreModels project — the same threads users see in the app's grid collaboration panel. Viewer access is required
- `list_projects`: List the user's CoreModels projects as [id,name,accessLevel] (see the response "format" field). Use a returned id as graphProjectId for other tools. Pass search
- `query_model_graphql`: Run a read-only GraphQL query against a CoreModels project's model — the general query escape hatch for precise questions (projections, traversals, counts) that
- `run_code`: Execute a JavaScript program that orchestrates this server's tools, and return only its result. Prefer this over many individual tool calls when a task needs se
- `schema_library_get_classifications`: Get available classification options for SchemaLibrary projects, used to categorize and tag projects. Optionally filter by classification name (partial match su
- `schema_library_get_metadata_options`: Get available metadata options for SchemaLibrary projects (access methods, types, licenses, formats, domains, audiences, model sizes). Use these IDs when creati
- `schema_library_get_use_case_types`: Get available use case types for SchemaLibrary projects. Use these types when creating new use cases for a project.
- `schema_library_projects_section`: Search and retrieve a filtered, paginated list of SchemaLibrary projects with advanced filtering options including metadata, classifications, and project attrib
- `schema_library_query_project`: Query and retrieve details of a SchemaLibrary project including metadata, classifications, likes, cover images, and user permissions. Authenticated callers rece
- `search_nodes`: Search nodes in a CoreModels project. Returns compact positional arrays; the response "format" field describes the layout. Filters (provide at least one of the 
- `suggest_ontology_terms`: Suggest ontology-term candidates for a schema node from the public EMBL-EBI Ontology Lookup Service (OLS). ADVISORY ONLY: this is a read-only search — it calls 
- `transform_schema`: Transform a schema from one format to another through the ARAMAI mapping engine. Formats: jsonschema | shex | avro | jsonld | sql | osi | osi-json | owl | linkm
- `validate_json`: Validate one or more JSON documents against a project's stored JSON Schema. The schema is regenerated from the project using the supplied configTypeId (the expo
- `whoami`: Who is calling: returns the identity and subscription plan of the MCP token in use. No project id needed. Returns { userId, name, email, organizationId, endpoin

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
