Bunce Logo
BunceBack

For AI assistants and agents

Bunce works with your AI assistant

Connect Claude, ChatGPT, Cursor or any MCP client to Bunce and let it read your rates, market and bookings with the same playbook Bunce’s own pricing agent follows. You choose the property and the permissions.

Bunce MCP server

https://api.bunce.app/mcp

Yes. Bunce runs an MCP server, so Claude, ChatGPT, Cursor or any assistant that speaks the Model Context Protocol can read your rates, your market and your bookings, and reason with the same playbook Bunce’s own agent follows. You choose which property it sees and what it may do, and you can switch it off at any time.

What the connection is

MCP, the Model Context Protocol, is the open standard AI assistants use to reach tools and knowledge outside themselves. Bunce publishes an MCP server at the address above. An assistant that connects to it signs in with your Bunce account, is shown the access you have issued, and then works under exactly that access: it reads what you let it read, proposes what you let it propose, and nothing else.

The Bunce Guide

The same guide Bunce’s own agent reads before acting: how prices are built, how the market is read, how proposals and approvals work, and what an owner’s standing instructions mean. Served page by page, on request.

Tools scoped to the access

Tools for exactly the areas you ticked — the pricing grid, demand and pickup, the competitor set and its prices, reports, the property’s memory — each one refusing anything outside the access.

The operating context

The property’s operating context in one call: currency, time zone, autonomy mode, the approval queue and the standing instructions, so an assistant starts a conversation already knowing where it stands.

Set it up in three steps

  1. 1

    Give your assistant access

    In Bunce, open your property’s settings and choose External access. Give the assistant a name you will recognise, tick what it may do — reading is the default — and say how long the access lasts.

  2. 2

    Add Bunce to your assistant

    Paste the Bunce address wherever your assistant asks for an MCP server. In Claude Code that is one command; in Claude, Cursor and most others it is a custom connector with this address.

  3. 3

    Sign in, then pick the access

    The first time it connects, your assistant sends you to Bunce’s ordinary sign-in. Once you are back, ask it to list your Bunce access and use the one for this property. From then on it just works.

Add Bunce to your assistant

Every assistant that supports remote MCP servers takes the same address. Two forms cover nearly all of them.

Claude Code

claude mcp add -t http bunce https://api.bunce.app/mcp

Then run /mcp and choose Bunce to sign in.

Claude, Cursor, and other clients

Add a custom connector, or an MCP server, with the address above. Where a client takes a configuration file, this block is what it wants:

{
  "mcpServers": {
    "bunce": {
      "type": "http",
      "url": "https://api.bunce.app/mcp"
    }
  }
}

What you can hand over

Access is given per property, one area at a time. Reading an area never lets an assistant change it; every change is its own permission, and a permission that spends money or reaches a person says so.

Bookings

Reservations, occupancy, and booking pace.

  • Read reservations, occupancy, and pickup.Reads only

Market

Competitor set, competitor prices, and external market scans.

  • Add, remove, and re-map tracked competitors.Changes your data
  • Read the competitor set and the prices already collected for it.Reads only
  • Trigger paid external competitor scans.Spends money

Memory

What the property agent remembers.

  • Read stored property knowledge.Reads only
  • Create, edit, and archive stored property knowledge.Changes your data

Messaging

Messages that leave Bunce and reach a person, and where they are delivered.

  • Change where notifications are delivered, and switch them off.Changes your data
  • Send messages to the property owner and stakeholders.Leaves Bunce

Pricing

Room rates, rate bounds, and pricing targets.

  • Commit price and bound changes to the property.Changes your data
  • Create pricing changes for the owner to review.Changes your data
  • Read prices, bounds, targets, and simulations.Reads only

Property

Property profile, room structure, and the event calendar.

  • Edit the property profile, room structure, and event calendar.Changes your data
  • Read the property profile, room structure, and event calendar.Reads only

Reports

Saved report definitions and their generated artifacts.

  • Create, edit, and delete saved report definitions.Changes your data
  • Read saved report definitions and previously generated artifacts.Reads only
  • Execute saved reports, which consumes the property analysis budget.Spends money

Support

Requests to Bunce's own engineering team.

  • Tell Bunce's engineers what this property's agent is missing.Leaves Bunce

Tasks

The property task ledger.

  • Create, update, and close tasks.Changes your data
  • Read the task ledger.Reads only

What stays in your hands

No keys
Your assistant signs in as you, through Bunce’s own sign-in. There are no API keys to create, copy or lose.
Read-only unless you say otherwise
Reading is the default. Proposing or applying prices, editing competitors and sending messages are separate permissions you tick on purpose.
Yours to switch off
Access ends when you say — after at most 90 days — and switching it off takes effect on the very next request.
Never more than you
An assistant can never do more on a property than you can. Every call it makes is recorded against the access you gave it.

For developers and agent builders

The server is a standard remote MCP server, and a standard client needs nothing Bunce-specific to reach it. The facts below are stated as the server implements them.

  • Protocol revision 2026-07-28, and only that one: no initialize handshake, no session. Streamable HTTP with JSON responses over POST; GET is not served. Every request carries its protocol version in _meta and in the MCP-Protocol-Version header, its method in Mcp-Method, and the tool or resource it names in Mcp-Name. server/discover returns the supported revision, capabilities and identity.
  • Authorisation: OAuth 2.1 with PKCE and a resource indicator. The server answers an unauthenticated request with 401 and a WWW-Authenticate challenge that names its protected-resource metadata.
  • Clients register themselves. Client ID Metadata Documents are the preferred path; Dynamic Client Registration is accepted for clients that still use it. Nothing is pre-registered for you.
  • Sign-in is the property owner’s Bunce account. A token carries who signed in and which client asked; it carries nothing about a property.
  • Every Bunce tool is listed from the first call, and the list never changes shape. A fresh session is unbound: call list_my_access to see the access the signed-in person has issued, then use_access with the reference of the one to act under. Until then every Bunce tool answers access_not_chosen; afterwards, a tool the access does not cover answers capability_not_granted and names the capability. The choice is remembered per client.
  • The Bunce Guide is served as resources under bunce://guide/ and through the bunce_guide tool, which walks the same tree one page at a time.
  • Every tool call is recorded and rate-limited per access. A call that changes something and is repeated with identical arguments within fifteen minutes is answered from the first result rather than run twice, so a transport retry is safe.
Server
https://api.bunce.app/mcp
Protected-resource metadata
https://api.bunce.app/.well-known/oauth-protected-resource
Machine-readable summary
/llms.txt

Not on Bunce yet?

Bunce prices Mews and Cloudbeds properties today. Book a 20-minute call and see it working with your rates — and with your assistant.

Book a demo