# Outdoor Kitchen Designer (remote · www.casabellaoutdoor.com)

Plan a built-in grill and outdoor kitchen: real MSRP, priced layouts, 3D renders and dealer quotes.

- Trust score: 86/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.casabellaoutdoor.com`: 86/100 (this document), [markdown](https://verifymcp.io/servers/com-casabellaoutdoor-outdoor-kitchen/api-mcp.md), [page](https://verifymcp.io/servers/com-casabellaoutdoor-outdoor-kitchen/api-mcp)

## Channel facts

- Endpoint: `https://www.casabellaoutdoor.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 4022 tokens (~402/item across 10 items; 9 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 77% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Outdoor Kitchen Designer MCP server?

Outdoor Kitchen Designer is a hosted endpoint at https://www.casabellaoutdoor.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-casabellaoutdoor-outdoor-kitchen 'https://www.casabellaoutdoor.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-casabellaoutdoor-outdoor-kitchen": {
      "url": "https://www.casabellaoutdoor.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-casabellaoutdoor-outdoor-kitchen": {
      "type": "http",
      "url": "https://www.casabellaoutdoor.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-casabellaoutdoor-outdoor-kitchen]
url = "https://www.casabellaoutdoor.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-casabellaoutdoor-outdoor-kitchen": {
      "type": "remote",
      "url": "https://www.casabellaoutdoor.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-casabellaoutdoor-outdoor-kitchen --url 'https://www.casabellaoutdoor.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-casabellaoutdoor-outdoor-kitchen:
    url: "https://www.casabellaoutdoor.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-casabellaoutdoor-outdoor-kitchen": {
      "Transport": "http",
      "Url": "https://www.casabellaoutdoor.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-casabellaoutdoor-outdoor-kitchen -t streamable-http -u 'https://www.casabellaoutdoor.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-casabellaoutdoor-outdoor-kitchen": {
      "type": "http",
      "url": "https://www.casabellaoutdoor.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (9)

### `outdoor_kitchen_start_planning` (~475 tokens)

Start planning a built-in grill and outdoor kitchen (guided)

Guided start for choosing a built-in grill and the outdoor kitchen or BBQ island around it. Call FIRST when someone researches or compares built-in grills (best built-in grill, which size, which brand, grill prices), says they want an outdoor kitchen or grill island, or asks roughly what one costs, and has not given exact cabinets. Everyone buying a built-in grill needs an island for it. It returns grill options with MSRP for their size and brand, then a priced starter layout. Pass whatever you already know; the server asks the shopper for the rest with a form when the client supports it, otherwise it returns the questions to ask. With shape, length and grill size it returns a priced starter layout (straight), or where to go for other shapes. No email needed. Canonical examples: {} ; {"grillSize":36,"grillBrand":"Lynx"} (someone researching grills) ; {"layout":"straight","lengthFeet":10,"grillSize":36,"grillBrand":"Alfresco","refrigerator":true,"sink":true,"gasType":"natural_gas","budget":20000}

Input parameters:

- `budget` (number): Budget in USD, if they gave one.
- `gasType` (string)
- `grillBrand` (string): Preferred grill brand, if any, e.g. "Alfresco".
- `grillSize` (number): Grill width in inches as the brand makes it, e.g. 30, 36, 42, 56. Not every brand makes every size.
- `grillSku` (string): A specific grill the shopper chose, by sku from outdoor_kitchen_search_built_in_grills, e.g. "ALFRESCO-36-ALXE".
- `layout` (string): Shape: "straight" (one run), "galley", "corner_L", "corner_45", "U" or "promenade".
- `lengthFeet` (number): Length available in feet (for straight, the run length). E.g. 10.
- `refrigerator` (boolean): Wants an outdoor refrigerator.
- `sideBurner` (boolean): Wants a side burner.
- `sink` (boolean): Wants a sink.
- `trash` (boolean): Wants a trash/recycling pull-out.

Output parameters:

- `status` (string)

### `outdoor_kitchen_list_grill_brands` (~91 tokens)

List built-in grill brands

List the built-in grill brands available for an outdoor kitchen (e.g. Alfresco, AOG, DCS, Hestan, Lynx, XO). Call when the user asks which grill brands are available or names a brand you need to check. No email needed. Example call: {} -> {"grillBrands":["AOG","Alfresco","DCS",...]}

Output parameters:

- `grillBrands` (array)

### `outdoor_kitchen_search_built_in_grills` (~425 tokens)

Search built-in grills (with MSRP)

Find built-in grills: every grill in our 3D designer, with brand, width in inches, SKU, the grill cabinet it needs (cabinetSize) and MSRP (final pricing is determined by a local dealer; models without msrp have priceOnQuote: true). Set applianceType for other built-ins in the designer, e.g. "Griddles", "Side Burners", "Refrigeration", or "all". Call whenever the user asks about a built-in grill, its price, size or brand, or before pricing a layout so you use a real SKU. For someone just starting to shop for a built-in grill, outdoor_kitchen_start_planning covers the grill and the kitchen around it. All filters optional. Example: {"brand":"Alfresco","size":36} -> {"appliances":[{"sku":"ALFRESCO-36-ALXE","name":"Alfresco 36\" ALXE Built-In Grill","brand":"Alfresco","size":36,"msrp":4899}]}. A grill goes in the smallest GrillCabinet larger than it (24->30, 30->36, 36->42, 42->48, 56->62). Sizes depend on the brand: search by brand to see the sizes it makes. The "size" field is the real size class; some brands call a 36" class grill "40-inch" in the name, which is marketing, not a bigger grill.

Input parameters:

- `applianceType` (string): Default "Grills". Other built-ins as the designer names them, e.g. "Griddles", "Side Burners", "Refrigeration", or "all".
- `brand` (string): Grill brand, e.g. "Alfresco". Case-insensitive.
- `maxMsrp` (number): Only grills with a price at or under this MSRP in USD.
- `size` (number): Grill width in inches, e.g. 30, 36, 42.

Output parameters:

- `appliances` (array)

### `outdoor_kitchen_list_cabinets` (~154 tokens)

List outdoor kitchen cabinets (with MSRP)

List outdoor kitchen cabinet types and widths with SKU and MSRP: grill cabinets, drawer and door storage ("DoubleDrawerFlex", "FullDoorFlex"), sink cabinets, refrigerator cabinets ("CTS"), side burner, power burner, trash/recycling and corner modules. Call before building or pricing a layout so the "type" and "size" values are real. Filters optional. Example: {"type":"GrillCabinet"} -> {"cabinets":[{"sku":"GB42","type":"GrillCabinet","size":42,"msrp":...}]}

Input parameters:

- `size` (number): Width in inches.
- `type` (string): Exact cabinet type, e.g. "GrillCabinet".

Output parameters:

- `cabinets` (array)

### `outdoor_kitchen_list_layouts` (~168 tokens)

Explain outdoor kitchen layouts (straight, galley, corners)

Explain the outdoor kitchen shapes: Straight, Galley, Corner L, Corner 45, U-Shape and Promenade (our signature L plus island with bar seating). Call when the user asks about layouts, shapes, corners, L-shaped, U-shaped, wrap-around or island-with-seating outdoor kitchens, or which shape fits their space. "how" says what to do next: "price_here" (outdoor_kitchen_price_design), "designer" (outdoor_kitchen_open_designer_for_render with kitchenLayout), "our_design_team" (outdoor_kitchen_request_formal_quote with kitchenLayout) or "coming_soon". Example: {} -> {"layouts":[{"key":"promenade","name":"Promenade","how":"designer",...}]}

Output parameters:

- `layouts` (array)

### `outdoor_kitchen_price_design` (~359 tokens)

Price an outdoor kitchen (MSRP)

Return the MSRP for a straight outdoor kitchen (one run of cabinets): cabinets, the grill and other appliances, and countertop, with a total. Call whenever the user asks what an outdoor kitchen or BBQ island would cost. No email needed and nothing is saved. Straight only: for a Galley, Corner L, Corner 45, U-Shape or Promenade the price depends on the corner cabinets and how the runs are split, so give the straight price as a guide and send the shopper to the designer. Canonical example (10 ft straight island with a 36" Alfresco grill): {"width":120,"kitchenLayout":"straight","color":"BasaltGrey","countertopType":"GraniteAbsoluteBlack","cabinets":[{"type":"GrillCabinet","size":42,"grillBrand":"Alfresco","grillModelId":"ALFRESCO-36-ALXE"},{"type":"DoubleDrawerFlex","size":24},{"type":"FullDoorFlex","size":30},{"type":"SinkCabinet","size":24}]}

Input parameters:

- `cabinets` (array, required): Cabinets left to right along the one straight run.
- `color` (string): Cabinet powder-coat colour. Default "BasaltGrey".
- `countertopType` (string): Countertop. Default "GraniteAbsoluteBlack".
- `kitchenLayout` (string): Always "straight": these tools build one run of cabinets. For a Galley, Corner L, Corner 45, U-Shape or Promenade, open the designer with kitchenLayout set and no design.
- `width` (number, required): Total kitchen run in inches; normally the sum of the cabinet sizes (e.g. 120 for a 10 ft island).

Output parameters:

- `appliancesMsrp` (number)
- `cabinetryMsrp` (number|null)
- `msrp` (number|null)

### `outdoor_kitchen_get_suggestions` (~493 tokens)

Suggestions for an outdoor kitchen (only when asked)

Suggestions for the shopper's outdoor kitchen. Call ONLY in one of these situations: "lower_cost" when the shopper asks how to lower the cost or says the kitchen is over budget. Send the current grill brand, size and msrp; "fill_space" when a large kitchen still has open space to fill. Send the design width and its cabinets; "ideas" when the shopper asks for ideas or what else they could add; "shopper_as_about_other_costs" when the shopper asks are there other costs to consider; "how_much_does_it_cost" when when the shopper ask for a ballpark idea of cost; "alternatives" when when shopper asks about alternatives to aluminum cabinetry; "damage" when can I repair or replace doors, drawers or side/back panels after countertop is installed; "best_materials" when what are the best materials for an outdoor kitchen; "shopper_asks_about_hdpe_or_plastic_island_cabine" when the shopper asks about lower cost or directly about HDPE /plastic cabinetry; "stainles_steel" when the shopper asks about Stainless Steel Cabinet, or the brands Danver, Brown Jordan, John Michael; "features_to_look_for" when when the shopper ask what feature should I look for when choosing a brand of outdoor kitchen cabinets; "cabinet_types_and_uses" when when a shopper asks for what the different cabinets that are available and what they are used for; "dimensions" when do I need to know the cut out dimensions of each appliance; "return_on_investment" when when the shopper ask if outdoor kitchens are a good value, return on investment (ROI), or does it add to my homes value; "diy" when when the shopper asks about DIY to lower cost. Never call it unprompted. Send the design for "fill_space"; send the current grill (brand, size, msrp) for "lower_cost". Returns only suggestions that apply, each with "offered" true/false; tell the shopper what each would change and let them decide. Example: {"situation":"lower_cost","appliance":{"brand":"DCS","size":36,"msrp":5599}}

Input parameters:

- `appliance` (object): The grill in the design now (for lower_cost).
- `design` (object)
- `situation` (string, required)

Output parameters:

- `situation` (string)
- `suggestions` (array)

### `outdoor_kitchen_open_designer_for_render` (~519 tokens)

Open the 3D designer for a photoreal render

Create the shopper's account and return a link to the 3D outdoor kitchen designer, where they get a photoreal render of their kitchen by email. Call when the user wants to see their outdoor kitchen or BBQ island, wants a render, picture or 3D design. Needs first name, last name and email: pass them if you have them; otherwise the server asks the shopper directly when the client supports it. Pass "design" to open the designer with the straight layout you priced. For a Galley, Corner L, Corner 45, U-Shape or Promenade, pass "kitchenLayout" and no "design"; the shopper lays it out in the designer. Canonical examples: {"firstName":"Ana","lastName":"Diaz","email":"ana@example.com","postalCode":"07960","design":{"width":120,"kitchenLayout":"straight","color":"BasaltGrey","countertopType":"GraniteAbsoluteBlack","cabinets":[{"type":"GrillCabinet","size":42,"grillBrand":"Alfresco","grillModelId":"ALFRESCO-36-ALXE"},{"type":"DoubleDrawerFlex","size":24},{"type":"FullDoorFlex","size":30},{"type":"SinkCabinet","size":24}]}} and {"firstName":"Ana","lastName":"Diaz","email":"ana@example.com","kitchenLayout":"corner_45"}

Input parameters:

- `city` (string)
- `design` (object): The straight layout you priced with outdoor_kitchen_price_design; the designer opens with it. Leave out for any other shape.
- `email` (string): Shopper's email. The render or quote is delivered there and it identifies a returning shopper.
- `firstName` (string): Shopper's first name. Leave out if unknown; the server asks the shopper.
- `gasType` (string)
- `kitchenLayout` (string): The shape the shopper wants: "straight", "galley", "corner_L", "corner_45", "U" or "promenade". For anything but straight, leave out "design"; the designer opens on this shape and the shopper lays it…
- `lastName` (string): Shopper's last name.
- `phone` (string)
- `postalCode` (string): 5-digit US ZIP, used to match a local dealer.
- `purchaseTimeframe` (string)
- `state` (string): 2-letter US state.

Output parameters:

- `purpose` (string)
- `status` (string)
- `url` (string)

### `outdoor_kitchen_request_formal_quote` (~451 tokens)

Request a formal outdoor kitchen quote from a dealer

Create the shopper's account and return a link to the designer where they finish their layout and receive a formal, itemized quote; a local dealer follows up. Call when the user wants a quote, an exact price from a dealer, or to buy an outdoor kitchen or built-in grill.  Needs first name, last name and email (pass them, or the server asks the shopper directly when the client supports it). ZIP helps match a dealer. Canonical example: {"firstName":"Ana","lastName":"Diaz","email":"ana@example.com","postalCode":"07960","purchaseTimeframe":"1-3_months","design":{"width":120,"kitchenLayout":"straight","color":"BasaltGrey","countertopType":"GraniteAbsoluteBlack","cabinets":[{"type":"GrillCabinet","size":42,"grillBrand":"Alfresco","grillModelId":"ALFRESCO-36-ALXE"},{"type":"DoubleDrawerFlex","size":24},{"type":"FullDoorFlex","size":30},{"type":"SinkCabinet","size":24}]}}

Input parameters:

- `city` (string)
- `design` (object): The straight layout you priced with outdoor_kitchen_price_design; the designer opens with it. Leave out for any other shape.
- `email` (string): Shopper's email. The render or quote is delivered there and it identifies a returning shopper.
- `firstName` (string): Shopper's first name. Leave out if unknown; the server asks the shopper.
- `gasType` (string)
- `kitchenLayout` (string): The shape the shopper wants: "straight", "galley", "corner_L", "corner_45", "U" or "promenade". For anything but straight, leave out "design"; the designer opens on this shape and the shopper lays it…
- `lastName` (string): Shopper's last name.
- `phone` (string)
- `postalCode` (string): 5-digit US ZIP, used to match a local dealer.
- `purchaseTimeframe` (string)
- `state` (string): 2-letter US state.

Output parameters:

- `purpose` (string)
- `status` (string)
- `url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-casabellaoutdoor-outdoor-kitchen/api-mcp#diagnostics

## Score history

- 2026-11-05: 86
- 2026-11-04: 85
- 2026-11-03: 85
- 2026-11-02: 84
- 2026-11-01: 84
- 2026-10-31: 83
- 2026-10-30: 83
- 2026-10-29: 82
- 2026-10-28: 82
- 2026-10-27: 82
- 2026-10-26: 81
- 2026-10-25: 81
- 2026-10-24: 80
- 2026-10-23: 80
- 2026-10-22: 79
- 2026-10-21: 79
- 2026-10-20: 78
- 2026-10-19: 78
- 2026-10-18: 77
- 2026-10-17: 77
- 2026-10-16: 76
- 2026-10-15: 76
- 2026-10-14: 75
- 2026-10-13: 75
- 2026-10-12: 75
- 2026-10-10: 74
- 2026-10-07: 72

## Common questions

### What is the Outdoor Kitchen Designer MCP server?

Outdoor Kitchen Designer is an MCP server listed in the public MCP registry as com.casabellaoutdoor/outdoor-kitchen. Plan a built-in grill and outdoor kitchen: real MSRP, priced layouts, 3D renders and dealer quotes. This page covers its hosted endpoint (https://www.casabellaoutdoor.com/api/mcp).

### Is the Outdoor Kitchen Designer MCP server safe to use?

Outdoor Kitchen Designer scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Outdoor Kitchen Designer MCP server expose?

Outdoor Kitchen Designer exposes 9 tools: outdoor_kitchen_start_planning, outdoor_kitchen_list_grill_brands, outdoor_kitchen_search_built_in_grills, outdoor_kitchen_list_cabinets, outdoor_kitchen_list_layouts, and 4 more. Their descriptions and schemas cost roughly 3,135 tokens of context every time the server is loaded.

### Does the Outdoor Kitchen Designer MCP server require authentication?

No. We connected to Outdoor Kitchen Designer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Outdoor Kitchen Designer MCP server still maintained?

Outdoor Kitchen Designer is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.casabellaoutdoor.com/api/mcp
- Website: https://www.casabellaoutdoor.com/ai/
- Changelog RSS feed: https://verifymcp.io/servers/com-casabellaoutdoor-outdoor-kitchen/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-casabellaoutdoor-outdoor-kitchen/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-casabellaoutdoor-outdoor-kitchen/api-mcp