Kitchen Studio MCP tool reference for AI assistants
Kitchen Studio's MCP integration exposes equipment search, account-scoped kitchen editing, layout checks and equipment schedules. Use https://kitchenstudio.design/mcp with a compatible remote MCP client and the account connection flow. Review the kitchen visually; PDF, SVG and CSV drawing exports are made in the editor.
Connection and access
Endpoint: https://kitchenstudio.design/mcp. The implementation uses bearer-token account authorization through the connection flow. A URL in the documentation does not establish that a particular client is connected or that its authenticated session succeeds. Test the intended client before depending on automated project work.
Units and coordinates
Use millimetres. The inside north-west corner is the origin: x increases east, y increases south. Catalogue keys identify the model selected by search_equipment. Preserve exact equipment dimensions rather than resizing a branded model to force a fit.
Equipment from quotations
Share the source document with your chosen MCP agent. Ask it to send equipment fields to prepare_equipment, resolve missing details and catalogue conflicts, then add_items to your selected kitchen and run check_layout. Preparation writes nothing; unknown utilities remain unknown and custom equipment stays unverified. Kitchen Studio does not call a model API. For software-only intake, upload the quotation in the desktop editor.
Available tools
| Tool | Purpose |
|---|---|
| prepare_equipment | Validate up to 50 equipment rows extracted by your agent or supplied by the user. No writes and no AI service call. Returns missing fields, unknown utilities, exact catalogue matches with conflicts, and custom payloads for add_items. Omit prices, customer details and instructions from documents. Never infer dimensions, mounting or utilities. Quantity is returned separately; each add_items entry places one unit. Custom records remain unverified. |
| search_equipment | Search Kitchen Studio's catalogue of real commercial kitchen equipment (published dimensions, power, kW, water/drain). Returns catalogue keys to use with add_items. |
| list_fabricated_types | Stainless items made to size (tables, sinks, shelves, hoods, pass shelves) and fabricated refrigeration (counter chillers, lowboys, saladettes), with default sizes and options. |
| list_kitchens | Kitchens saved in the user's Kitchen Studio account. |
| get_kitchen | Room size, every item with its number (as in the app), id, position, size, what it sits on, loads, openings, and layout checks. |
| create_kitchen | New empty kitchen in the user's account (rectangular room). |
| update_kitchen | Change the name or the room size. |
| add_items | Add catalogue equipment, fabricated stainless/refrigeration, custom equipment, or doors/columns/service points. Returns the new ids and the layout checks. |
| update_items | Move items (wall/offset, x/y/rot, on_top_of), change size/height/z/kw/options of fabricated and custom items, or rename them. Catalogue models keep their spec-sheet size. |
| remove_items | Remove items from a kitchen by id. |
| check_layout | Overlaps, items outside the room, blocked door swings, countertop items with no base, cooking equipment not under a hood. |
| get_schedule | Equipment list with power, kW, water and drain, and the electrical/gas/water/drain totals. (Drawing exports are made in the app.) |
A small workflow to verify
- Connect the intended account and list its kitchens, or create a separate test kitchen with known room dimensions.
- Search for exact equipment, add the selected items and inspect the returned layout checks.
- Open the result in the editor, compare dimensions and confirm the saved project is the intended one.
- Retrieve its schedule and use the visual editor for drawing exports.
- Exercise missing-model, impossible-fit, retry and concurrent-edit cases before promising unattended operation.
Integration boundaries
The machine-readable reference is generated from the same exported tool definitions as the server. Local schema and test results describe the reviewed source; they do not establish a successful deployed or external-client session. Keep unknown equipment services and installation requirements explicit. The integration does not provide engineering approval, payment processing or drawing-file exports.