CoreModels MCP Server

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 exportTypes/exportElements/exportTaxonomies/exportDataTypes must be true. Tree-based mode (graphBased=false) requires exactly one nodeId; graph-based mode allows multiple or none.

Export project data as a JSON Schema string.

Export project data as a ShEx (Shape Expressions) schema string.

Create a new mixin type. Check existing mixins first with get_mixins_and_relation_groups to avoid duplicates. Mixins are reusable property sets applicable to any node.

Create a mixin value for a node. mixinId and column ids come from get_mixins_and_relation_groups. A node can have multiple mixins; each mixin can have multiple columns.

Remove one or more mixin column values from a node. mixinId and column ids come from get_mixins_and_relation_groups. This does not delete the mixin definition itself.

Create a new node. Empty/omitted spaceIds = default space; MUST be empty when nodeType is 'Space'.

Suspend a node.

Update an existing node's label and/or its space assignments. Omitted fields are unchanged. spaceIds replaces (not merges) existing assignments; empty array = default space. At least one of label or spaceIds must be provided.

Create a directed relation fromNodeId → toNodeId. relationGroupId is the relation template; list templates with get_mixins_and_relation_groups.

Create a new relation group (a 'class' defining valid source→target node-type combinations for relations). Always call get_mixins_and_relation_groups first — duplicate labels are rejected. Allowed mappings: Type, Element, Name Spaces, Spaces, Components, Component Tag, Exemplar, Taxonomy.

Remove a relation between two nodes.

Get information about all mixins in a CoreModels project. Mixins define structured metadata used for mapping models, system integrations, and other extensions. Use get_node tool documentation to understand how mixins are attached to nodes.

Get information about relation groups for a CoreModels project. Use the relation groups to create a relation between two nodes.

Fetch JSON-LD import/export profiles available for a project.

Fetch JSON Schema import/export profiles available for a project.

Create a new CoreModels project owned by the calling user, including a ready-to-use default space. Returns { projectId, defaultSpaceId }; use projectId as graphProjectId and defaultSpaceId as a spaceId in other tools (e.g. import_jsonschema). Projects are created private in the caller's default workspace. Fails (no silent duplicate) if the caller already has a project with the same name.

Labels and IDs of types, elements, and taxonomies in the project. Each category is paginated independently. Pagination: - First call: omit page (defaults to 0). - Each category reports page, pageSize and hasMore. Re-request with page+1 for any category whose hasMore is true.

Create multiple nodes, relations, and mixin values in one atomic operation. When to use: - Creating more than one node. - Any creation that includes relations and/or mixins. - For a single node with no relations/mixins, prefer create_node. Required ids come from: - get_mixins_and_relation_groups: relationGroupId, mixinId, and each mixin column id. - get_project_summary or search_nodes (nodeType=Space): spaceIds, plus any existing nodeIds you want to reference. Relation endpoints (fromNodeId / toNodeId) may be either: - ids of nodes created elsewhere in this same payload, or - ids of nodes already in the project.

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 several steps, looping, filtering, or combining data: intermediate results stay in the sandbox, so only what you return reaches the model. Inside the script: - listTools() -> [{name, summary}] discover available tools - getToolDoc(name) -> {name, description, parameters, required} inspect one tool's inputs - tools.<name>(args) -> parsed result call a tool (graphProjectId is injected automatically; do NOT pass it) - console.log(...) captured and returned alongside the result - return <value> JSON-serialized and returned Environment: sandboxed JavaScript, no network or filesystem, with limits on time, memory, statements and number of tool calls. Currently only read-only tools are callable from code.

Generate an AI summary of the project (from its types, elements and taxonomies) and save it as the project's markdown AI summary. Returns the generated summary. If a summary already exists it is returned unchanged unless regenerateIfStale=true (default) and the project has been updated since the summary was generated (stale). Requires the user to have a Claude API key configured in ChatBot settings.

Imports a JSON Schema into a space

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 tools (mixinId, columnId, relationGroupId). Returns compact positional arrays - see the "format" field for the layout.

Search nodes in a CoreModels project. Returns compact positional arrays; the response "format" field describes the layout. Filters (provide at least one; they combine with AND): - nodeIds: exact id lookup - nodeType: one of Element, Type, Taxonomy, Exemplar, Component, Space, Tag, Mixin - expression: partial substring match on the node label (plain text, no wildcards) - spaceIds: restrict to specific spaces Optional flags: includeRelations, includeMixins, sortAttr, sortDesc, pageSize. Pagination: - First call: omit pagingToken. - If the response has a pagingToken, more pages exist. Repeat the same call with that exact token to get the next page. - If the response has no pagingToken, this was the last page.

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 searchTerm to filter by name (case-insensitive substring). Set includePublicProjects=true to also include public projects. Set includeAISummary=true to also return each project's saved AI-generated summary and the time it was generated (4th and 5th elements). Paged: page is 1-based; increment page up to the returned totalPages to get all results.

Validate a JSON document against a project's stored JSON Schema. The schema is regenerated from the project using the supplied configTypeId (the export profile id) and rootNodeId. Provide the JSON to validate as a serialized string.