Removing a node is a soft delete with core_models_restore_node as its undo, but removing a relation, a mixin value or a mixin type is final, and dropping a mixin type also drops every column defined on it. Build with core_models_bulk_create rather than a call per element, and read core_models_project_content_summary first so proposed changes are made against what the project actually contains rather than what an agent assumes. Every call carries its own token, which means the credential is a tool argument and not something the connection remembers for you.
A remote MCP server at https://go.coremodels.io/mcp for CoreModels, where a data model is a graph of nodes: types, elements, relations, mixins and taxonomies. Four read tools report what a project already holds, eight build it out, and four remove things — with the removals graded by how permanent they are.
- core_models_fetch_nodes reads nodes with filtering and pagination, and core_models_project_content_summary returns every type, element and taxonomy in the project at once
- core_models_get_mixins_info and core_models_get_relation_groups_info report the mixin definitions and relation groups you have to build with
- core_models_create_node adds a node, core_models_update_node changes its label or spaces, and core_models_create_relation connects two of them
- core_models_bulk_create lands nodes, relations and mixins in a single call instead of one call per element
- Mixins carry the metadata: core_models_create_mixin_type defines one with its columns, and core_models_create_mixin_value attaches values to a node
- core_models_import_jsonschema brings an existing JSON Schema into a space
- core_models_remove_node is a soft delete that core_models_restore_node reverses; core_models_remove_relation, core_models_remove_mixin_value and core_models_remove_mixin_type are permanent, and the last takes every column on that mixin type with it
Nothing to install — point the client at https://go.coremodels.io/mcp over streamable HTTP. Authentication is per call rather than per connection: every tool takes a token parameter, and the API key is generated from your CoreModels project settings.
One command plus a key — npx -y mcp-remote https://go.coremodels.io/mcp, then supply credentials