Direct answer

Yes, Wheelhouse has an official MCP server. Announced July 2, 2026, it exposes 58 tools built on the Wheelhouse Revenue Management APIs, with what Wheelhouse describes as 1:1 parity with the Wheelhouse UI. To connect it to Claude, enable MCP access on the Api Key page of your Wheelhouse dashboard, then add the endpoint https://mcp.usewheelhouse.com/mcp as a custom connector in Claude and sign in through the OAuth prompt. Setup takes about two minutes and requires no code. The server is read-write: Claude can read prices, comps, and reservations, and can also change pricing preferences if you ask it to.

58 tools
1:1 parity with the Wheelhouse UI, per Wheelhouse's announcement
Jul 2026
Official MCP server announced July 2, 2026
OAuth
Sign-in via WorkOS AuthKit, no key pasting
$0 beta
RM API is in free beta; paid once officially released

How the connection works

Wheelhouse took the hosted route. According to the Wheelhouse changelog (July 2026), the MCP server connects "AI coding assistants and chat clients" including Claude, Cursor, and VS Code directly to your Wheelhouse account, with access tied to each user's account. Under the hood it sits on the Wheelhouse Revenue Management API. According to Wheelhouse's RM API reference, when you use the API through the MCP server you authenticate with OAuth via WorkOS AuthKit, and the server attaches your RM API key to requests automatically. You never handle the key yourself.

Claude

Web, Desktop, or Claude Code with the connector added

OAuth sign-in

WorkOS AuthKit browser prompt, your Wheelhouse login

Your Wheelhouse account

58 tools: prices, comps, reservations, preferences

This connector can write, not just read

Wheelhouse is explicit about this. In its announcement it says you are "not working with a simplified read-only layer": the MCP server exposes "the same data and levers your team uses inside the Wheelhouse UI," including pricing preferences, min/max rules, custom rates, reservations, and comp data.

That is powerful and worth respecting. Keep exploratory sessions to read-style questions, and when you do want Claude to change a preference or set a custom rate, ask it to show you the exact change before it runs the tool. Our PriceLabs guide ships read-only by design; Wheelhouse's official server does not have a documented read-only mode, so the discipline lives in how you prompt.

What you can ask Claude once connected

These map to what Wheelhouse says the tools cover: price recommendations, listing preferences, custom rates, reservations, KPIs, and market and neighborhood-level pricing and occupancy data.

Pricing"Pull next month's price recommendations for every listing and flag any night where the recommendation sits at my minimum price."
Comps"How does my downtown 2BR's pricing compare to its neighborhood comps for the next 60 days?"
Portfolio"Which listings have the lowest occupancy pace versus their market this quarter? Rank them."
Revenue"Summarize last month's reservations by listing: nights sold, ADR, and total revenue."
Settings"List every listing where the minimum price is within 10 percent of the base price, so I can review whether the floor is choking bookings."
Owner comms"Draft an owner update for Unit 14: how it priced against the neighborhood, what booked, and what we changed."

Prerequisites

  • A Wheelhouse account with your listings connected. MCP access and usage is tied to your user account within Wheelhouse.
  • Claude on the web, Claude Desktop, or the Claude Code CLI. According to Anthropic's help center, custom connectors are available on Free, Pro, Max, Team, and Enterprise plans (Free is limited to one custom connector).
  • Nothing else. No Node.js, no local server, no config file editing. That is the practical difference from the DIY setups elsewhere in this series.

Setup walkthrough

01

Enable MCP access in Wheelhouse

Wheelhouse's announcement describes the flow as: open your account's API Key area and enable MCP access. In the current dashboard, the Api Key page lives under your profile menu:

  1. Log in to Wheelhouse and click your profile name in the top-right corner.
  2. Select Api Key from the dropdown.
  3. Enable MCP Access. Wheelhouse shows client-specific setup instructions here for Claude, Cursor, VS Code, and other MCP clients.

You do not need to copy an API key for the MCP route. Per the RM API reference, the OAuth flow attaches your RM key to requests server-side. (Manual RM API keys exist on the same page if you ever want to hit the API directly.)

02

Add the connector to Claude

The endpoint is the same for every client:

Wheelhouse MCP endpoint
https://mcp.usewheelhouse.com/mcp

Claude web and Claude Desktop

Custom connector, point and click
  1. Open Settings, then Connectors.
  2. Click Add custom connector.
  3. Paste https://mcp.usewheelhouse.com/mcp as the server URL and click Add.

On Team and Enterprise plans an Owner adds the connector under Organization settings first; members then hit Connect on it.

Claude Code (CLI)

One command in your terminal
Terminal 
claude mcp add --transport http wheelhouse \
  https://mcp.usewheelhouse.com/mcp

Then run /mcp inside Claude Code to trigger authentication.

03

Sign in when the OAuth prompt appears

The first time Claude touches the connector, your browser opens a hosted sign-in page (WorkOS AuthKit). Log in with your Wheelhouse credentials and approve access. There is no token to paste anywhere; the authorization is stored by your Claude client and scoped to your Wheelhouse user account.

04

Enable it in a conversation and test

In Claude web or Desktop, open a new chat, click the tools menu, and make sure the Wheelhouse connector is toggled on. Then ask something that forces a real round trip:

Try it

"List my Wheelhouse listings in a table with base price and minimum price, then tell me which one you'd review first and why."

Troubleshooting

401 "invalid_token" or authentication failed

The server's own error message tells you the fix: "clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens." In Claude web or Desktop, disconnect the Wheelhouse connector in Settings, then reconnect and run the OAuth sign-in again. In Claude Code, run /mcp and re-authenticate the wheelhouse server.

Claude doesn't show any Wheelhouse tools

Three usual causes. First, the connector is added but not enabled for the current conversation; check the tools menu in the chat input. Second, MCP Access was never enabled on your Wheelhouse Api Key page (Step 1). Third, on Claude Desktop, restart the app after adding a connector so it picks up the new configuration.

"Add custom connector" is missing or greyed out

According to Anthropic's help center, custom connectors are available on Free, Pro, Max, Team, and Enterprise plans, but Free accounts are limited to one custom connector, and on Team and Enterprise plans only an organization Owner can add one. If you're on a work plan, ask your Owner to add the Wheelhouse endpoint under Organization settings, then connect to it from your own Settings.

429 Too Many Requests on big portfolio queries

Wheelhouse's RM API reference documents a rate limit of 60 requests per minute. A portfolio-wide question can fan out into dozens of tool calls. If Claude hits a 429, ask it to work in smaller batches ("do 10 listings at a time") or narrow the date range.

I want read-only access

Wheelhouse's hosted server doesn't document a read-only mode; it advertises full parity with the UI. If you want a hard guarantee that Claude can never write, you can build a small local MCP server that only wraps the RM API's read endpoints (listings, recommendations, reservations, market reports), using your RM API key with the X-Integration-Api-Key header against https://api.usewheelhouse.com/ss_api/v1/. Our PriceLabs guide shows exactly that pattern end to end.

FAQ

Does Wheelhouse have an official MCP server?

Yes. Wheelhouse announced it on July 2, 2026 in its changelog under the title "Wheelhouse MCP: Your Entire Platform, API-First." It exposes 58 tools built on the Revenue Management APIs and works with Claude, Cursor, VS Code, and other MCP clients. The endpoint is https://mcp.usewheelhouse.com/mcp.

Is the Wheelhouse MCP server read-only?

No. Wheelhouse states you get "the same data and levers your team uses inside the Wheelhouse UI": pricing preferences, min/max rules, reservations, comp data, and custom rates. Claude can change settings if you ask it to, so review write requests before approving them.

Does it cost extra?

As of July 2026, Wheelhouse's help center says the RM API is "currently in free beta" and "will become a paid feature once it is officially released." MCP access is tied to your Wheelhouse user account. On the Claude side, custom connectors are available on every plan including Free (which allows one).

Can I skip MCP and use the Wheelhouse API directly?

Yes. Wheelhouse publishes several APIs: the Revenue Management API (full account access, the one MCP is built on), the Wheelhouse Pro API and Lite API for price recommendations, a Demand Signal API, and Market and Comps APIs available by request to partners@usewheelhouse.com. Direct RM API calls authenticate with an X-Integration-Api-Key header. For chatting with your data in Claude, the hosted MCP server is the shortest path.

How does this compare to connecting PriceLabs to Claude?

As of July 2026, PriceLabs has no official MCP server, so our PriceLabs guide walks you through building a small local one on the PriceLabs Customer API, which is billed at $1 per synced listing per month. Wheelhouse hosts an official server, so setup is paste-a-URL-and-sign-in. If you run both tools, the two guides side by side make a fair head-to-head of the DIY and hosted approaches.

Pricing is half the picture

Once Claude can see your rates, the natural next question is whether it can see the units themselves. Pricing data tells you what a night is worth; it doesn't tell you the hot tub cover is cracked or the turnover missed the guest bathroom. That's the other half we care about: RapidEye analyzes turnover photos and walkthrough video to catch damage and missed work, and its API can sit in the same Claude conversation as your Wheelhouse connector, so "how is Unit 14 priced" and "what condition is Unit 14 in" get answered in one place.

Browse the rest of the series at /claude-guides/: PMS connections (Guesty, Hostaway, OwnerRez, Hostfully, Hospitable), operations tools (Turno, Operto Teams), guest screening (Safely), smart locks (Seam), and the PriceLabs sibling to this page.

Dynamic pricing

Connect PriceLabs to Claude

No official MCP there yet, so we build a read-only server on the Customer API. The DIY counterpart to this page.
PMS

Connect OwnerRez to Claude

Bookings, properties, guests, and payments through a personal access token.
PMS

Connect Hostaway to Claude

Listings, reservations, calendar, and tasks in plain English from one of the biggest PMS platforms.