kernelcad

Get Project

get_project

Read-only

Use this when you need to reopen a saved project or browse what the user has saved — it fetches a kernelCAD Studio project, or lists the signed-in user's saved projects. Pass slug (from a /p/ link or a prior listing) to fetch that project's full .kcad source and metadata — then edit and open_in_studio with the same slug so the user's open tab updates live. Private projects require their owner's OAuth connection. OMIT slug to list the signed-in user's saved projects (most recently updated first); that listing mode requires the OAuth connection.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	No	The project slug from a listing or a /p/<slug> Studio link. Omit to list the signed-in user's saved projects.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	No	Whether the read succeeded.
`url`	No	Fetch mode: revision-pinned /p/<slug>?version= link.
`code`	No	Fetch mode: the full .kcad source.
`slug`	No	Fetch mode: the project slug.
`title`	No	Fetch mode: the project title.
`assets`	No	Complementary files keyed by source-relative path.
`meshUrl`	No	Fetch mode: revision-matched mesh artifact URL when available — FunnelViewer loads it instead of re-executing CAD. When meshStatus is building, this is the expected CDN URL (retry until ready).
`privacy`	No	Fetch mode: the project privacy.
`version`	No	Fetch mode: the project version.
`embedUrl`	No	Fetch mode: revision-pinned chrome-free /embed/<slug>?revision= viewer URL (includes meshUrl when available).
`projects`	No	List mode (no slug): the user's saved projects.
`meshError`	No	Fetch mode: sanitized repair/persist error when meshStatus is failed.
`meshStatus`	No	Fetch mode: ready \| building \| failed \| missing — explicit CDN artifact state (never silently omit meshUrl under CDN mode).
`parameters`	No	Fetch mode: the model's editable parameters.
`updated_at`	No	Fetch mode: last-updated timestamp.
`serverBuild`	No	Deploy identity (package+git SHA@boot time) so connector lag is observable.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 23, 2026

addedOutput schema / properties / meshError

Added value: +{
+  "description": "Fetch mode: sanitized repair/persist error when meshStatus is failed.",
+  "type": "string"
+}

addedOutput schema / properties / meshStatus

Added value: +{
+  "description": "Fetch mode: ready | building | failed | missing — explicit CDN artifact state (never silently omit meshUrl under CDN mode).",
+  "type": "string"
+}

changedOutput schema / properties / meshUrl / description

Previous value: -"Fetch mode: revision-matched mesh artifact URL when available — FunnelViewer loads it instead of re-executing CAD."New value: +"Fetch mode: revision-matched mesh artifact URL when available — FunnelViewer loads it instead of re-executing CAD. When meshStatus is building, this is the expected CDN URL (retry until ready)."

Changed4 schema fields changedSep 22, 2026

addedOutput schema / properties / embedUrl

Added value: +{
+  "description": "Fetch mode: revision-pinned chrome-free /embed/<slug>?revision= viewer URL (includes meshUrl when available).",
+  "type": "string"
+}

addedOutput schema / properties / meshUrl

Added value: +{
+  "description": "Fetch mode: revision-matched mesh artifact URL when available — FunnelViewer loads it instead of re-executing CAD.",
+  "type": "string"
+}

addedOutput schema / properties / serverBuild

Added value: +{
+  "description": "Deploy identity (package+git SHA@boot time) so connector lag is observable.",
+  "type": "string"
+}

addedOutput schema / properties / url

Added value: +{
+  "description": "Fetch mode: revision-pinned /p/<slug>?version= link.",
+  "type": "string"
+}

Changed1 schema field changedJul 27, 2026

addedOutput schema / properties / assets

Added value: +{
+  "additionalProperties": true,
+  "description": "Complementary files keyed by source-relative path.",
+  "type": "object"
+}

Changed1 schema field changedJun 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "code": {
+      "description": "Fetch mode: the full .kcad source.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the read succeeded.",
+      "type": "boolean"
+    },
+    "parameters": {
+      "description": "Fetch mode: the model's editable parameters.",
+      "items": {},
+      "type": "array"
+    },
+    "privacy": {
+      "description": "Fetch mode: the project privacy.",
+      "type": "string"
+    },
+    "projects": {
+      "description": "List mode (no slug): the user's saved projects.",
+      "items": {},
+      "type": "array"
+    },
+    "slug": {
+      "description": "Fetch mode: the project slug.",
+      "type": "string"
+    },
+    "title": {
+      "description": "Fetch mode: the project title.",
+      "type": "string"
+    },
+    "updated_at": {
+      "description": "Fetch mode: last-updated timestamp.",
+      "type": "string"
+    },
+    "version": {
+      "description": "Fetch mode: the project version.",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedJun 13, 2026

changedInput schema / properties / slug / description

Previous value: -"The project slug from list_my_projects or a /p/<slug> Studio link."New value: +"The project slug from a listing or a /p/<slug> Studio link. Omit to list the signed-in user's saved projects."

removedInput schema / required
```
Removed value: -[
-  "slug"
-]
```

AddedJun 10, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark readOnlyHint and openWorldHint, so the safety profile is covered. The description adds meaningful behavioral context: returns full .kcad source and metadata, lists most recently updated first, requires OAuth for private/listing access, and notes that using the same slug with open_in_studio keeps the user's tab live.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core use case and organized into fetch vs. list modes. There is slight redundancy in mentioning OAuth twice (private projects and listing mode), but the description remains tight and readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Fully sufficient for a single-parameter, read-only tool with an output schema. It covers modes, prerequisites, auth, ordering, and integration with open_in_studio; nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the slug parameter is described there, but the description adds real value beyond it: where the slug comes from (/p/<slug> links or prior listings), what happens if omitted, and the downstream requirement to reuse the same slug with open_in_studio.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states a read-only tool for reopening or browsing saved kernelCAD Studio projects, with two explicit modes: fetch by slug or list the user's projects. It is easily distinguishable from siblings like open_in_studio and get_project_revision.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use guidance ('reopen a saved project or browse what the user has saved'), plus concrete routing: pass slug to fetch, omit slug to list. Auth requirements for private projects and listing mode are also stated, and the follow-up with open_in_studio is explained.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All kernelcad tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.