get_project_summaryLABSCO SUMMARY
Reading and writing are two separate connections.
Because changes go through their own connection, you can give every assistant the read-only one and add the admin one only where writing is meant to happen.
What it is
CoreModels' hosted MCP server, which lets an assistant work from the data model your team keeps in CoreModels instead of inventing a schema from memory. It comes as two connections: a read-only one, and an admin one for imports and changes.
What you get
- Project overview and search: list the projects you can see, get a project's types, elements and taxonomies with get_project_summary, and find nodes by name with search_nodes
- The mixins and relation groups a project is built from, including the Domain Includes links that tie each type to its fields — get_mixins_and_relation_groups
- A stored type exported as JSON Schema — export_jsonschema
- Conversion between JSON Schema, Avro, SQL, LinkML, ShEx, JSON-LD, OWL, Protocol Buffers, ODCS and more, with a note of what the conversion lost — transform_schema
- A JSON document checked against a type in the project, using the live model — validate_json
- On the admin connection: imports and updates, such as bringing in a dbt manifest or adding a JSON Schema as a new type
Requirements
Nothing to install. Sign in to CoreModels through OAuth in a client that supports it, such as Claude Code, or send a personal API key from your CoreModels account settings as a Bearer token. Both connections need one of the two, and writing through the admin one also needs Admin membership on the project.
Setup effort
Paste a URL, then authorize — add the servers you want to your client, then approve the OAuth consent screen
USE CASES
01
Understanding a data model you inherited
Get every type, element and taxonomy in the project in one summary, then see which fields belong to which type through its relation groups.
02
Working out which type a JSON sample belongs to
Search for each field, check every type that contains all of them before picking one, and confirm the match by validating the sample.
03
Checking a payload before it ships
Validate a JSON document against a type in the project and get the failing fields named, checked against the live model rather than a saved copy.
04
Converting a schema to another format
Hand over a JSON Schema and get Avro, Postgres DDL or another format back, with a note of what the conversion lost.
05
Importing a model or adding a type
Connect the admin connection to import a dbt manifest or add a JSON Schema as a new type.
6 tools
Listed in project docs. Your client may show a different list.
search_nodesget_mixins_and_relation_groupsexport_jsonschemavalidate_jsontransform_schemaBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation. These six are the tools CoreModels' own page names, all on the read-only connection. It does not name the admin connection's write tools; your client lists them once you connect and sign in.
Requires
- A client that can reach a remote MCP server over HTTP
- A CoreModels API key as a bearer token (generate it in your CoreModels account settings), or OAuth in a client that supports it
- Admin membership on the project, for the write tools on https://go.coremodels.io/mcp-admin
Where it runs
All 5 documented setups connect to a hosted endpoint.
INSTALLATION
Connect your client
ARAMAI hosts 2 servers, each with its own URL.
Server setup
coremodels
ENDPOINT URL
https://go.coremodels.io/mcpRequirements
- A CoreModels API key as a bearer token (generate it in your CoreModels account settings), or OAuth in a client that supports it
- Admin membership on the project, for the write tools on https://go.coremodels.io/mcp-admin
coremodels-admin
ENDPOINT URL
https://go.coremodels.io/mcp-adminRequirements
- A CoreModels API key as a bearer token (generate it in your CoreModels account settings), or OAuth in a client that supports it
- Admin membership on the project, for the write tools on https://go.coremodels.io/mcp-admin
MCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"coremodels": {
"url": "https://go.coremodels.io/mcp",
"headers": {
"Authorization": "Bearer <YOUR_CORE_MODELS_API_KEY>"
}
}
}
}Use the admin block only when the agent should be allowed to write.
VS Code
VS CODE · JSON
{
"servers": {
"coremodels": {
"type": "http",
"url": "https://go.coremodels.io/mcp"
}
}
}Cursor — Admin
CURSOR — ADMIN · JSON
{
"mcpServers": {
"coremodels-admin": {
"url": "https://go.coremodels.io/mcp-admin",
"headers": {
"Authorization": "Bearer <YOUR_CORE_MODELS_API_KEY>"
}
}
}
}Write tools on the admin endpoint still require Admin membership on the project.
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --transport http coremodels https://go.coremodels.io/mcpAdd the HTTP server, then complete OAuth when the client prompts you.
Claude Code — Admin
CLAUDE CODE — ADMIN · TERMINAL
claude mcp add --transport http coremodels-admin https://go.coremodels.io/mcp-adminAdd the admin server only if the agent needs write tools.
