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.

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.

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.

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.

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.

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.