Can Claude change my prices through the Beyond MCP server?

Beyond does not publish a tool-by-tool list for the MCP server. Access is gated behind a single OAuth scope, neyoba:ask, which frames the connection as assistant-style questioning of your account data. Treat the connection as live account access: review anything Claude proposes in the Beyond dashboard before acting, and revoke access any time by removing the connector in Claude.

Neyoba is Beyond's AI pricing assistant, launched in late 2025. According to Beyond's June 2026 announcement, more than 15,000 hosts and property managers had nearly 50,000 conversations with it in its first six months. The MCP server runs on the same subdomain (neyoba.beyondpricing.com) and its OAuth scope is neyoba:ask.

Does the Beyond MCP server work with ChatGPT too?

Yes. Beyond's developer documentation explicitly handles both discovery paths: spec-compliant clients like Claude follow the protected-resource metadata to the authorization server, while clients like ChatGPT read authorization-server metadata from the MCP server's own origin. Both end up with an equivalent OAuth flow.

How is this different from connecting PriceLabs to Claude?

PriceLabs has a self-serve Customer API but no official MCP server, so connecting it to Claude means running a small local MCP server yourself. Beyond hosts the MCP server first-party: you paste one URL into Claude as a custom connector and sign in. No Node.js, no config file, no key management.

Connect Beyond to Claude: Official MCP Server

Official first-party server ~5 minute setup OAuth sign-in, no keys Beta

The short answer

Yes, you can connect Beyond to Claude, and unlike most of the short-term rental stack you do not have to build anything. Beyond (formerly Beyond Pricing) announced an official Model Context Protocol server on June 23, 2026, describing it as the first MCP server for revenue management, currently in beta. The server lives at neyoba.beyondpricing.com/mcp. You add that URL to Claude as a custom connector, Claude opens Beyond's sign-in page, you approve access, and Claude can then work with your Beyond dynamic pricing data in plain English. Setup takes about five minutes and involves zero API keys.

Beyond MCP server, at a glance Beta since June 2026

Server URL

https://neyoba.beyondpricing.com/mcp

Authorization server

https://developers.beyondpricing.com

Sign-in / consent page

https://v2.beyondpricing.com/oauth/authorize

Auth model

OAuth 2.0 Authorization Code with PKCE (S256), public client, dynamic client registration

Required scope

neyoba:ask

Works with

Claude (claude.ai, Claude Desktop, Claude Code), ChatGPT, and other MCP clients

Why this guide has no code in it

Most tools in the STR stack do not speak MCP yet, so "connect X to Claude" usually means writing a small local server that wraps the vendor's REST API. That is exactly what our PriceLabs guide does, and it works well, but you end up managing a Node.js process and an API key.

Beyond skipped that step. According to Beyond's June 23, 2026 announcement, its MCP server lets AI tools like Claude, ChatGPT, and custom enterprise agents connect directly to Beyond's dynamic pricing data, and the company positions it as the first MCP server for revenue management. Beyond hosts the server; you just authorize it.

The usual way (PriceLabs, most PMSs)

Build a wrapper yourself

Generate an API key, install Node.js, write an MCP server, register it in a config file, restart Claude, keep the key safe.

The Beyond way

Paste one URL and sign in

Add https://neyoba.beyondpricing.com/mcp as a custom connector. Claude opens Beyond's login, you click approve, and OAuth with PKCE handles the credentials. Nothing to install, nothing to rotate, revocable any time.

What you can ask Claude once it's connected

Beyond's platform data covers listings, calendars, comp sets, and price recommendations (those are the resource categories its developer docs organize the API around). The natural fit is revenue management work that normally means tab-hopping and CSV exports:

Rate strategy "Review my base prices across the portfolio. Which listings look out of line with their recommendations, and by how much?"

Seasonality "How do my recommended rates move between July and October for the beach units? Summarize the shape of the season."

Portfolio health "Give me a pricing health check: flag listings where the calendar shows long open stretches inside 30 days."

Comp sets "How does my downtown two-bedroom sit against its comp set for the next 60 days?"

Reporting "Turn this into a Monday-morning summary I can paste to the owner: what changed in our pricing last week and why."

The beta does not publish a tool-by-tool capability list, so exact coverage may differ from account to account. Treat these as the shape of the questions, then probe what your connection actually exposes (ask Claude "what Beyond tools do you have?").

Where this came from: Neyoba

The MCP server did not appear out of nowhere. Beyond shipped Neyoba, its in-app AI pricing assistant, in late 2025, and the MCP server runs on the same subdomain with an OAuth scope named after it (neyoba:ask). According to Beyond's June 2026 announcement:

15,000+

hosts and property managers used Neyoba in its first six months

~50,000

conversations with the assistant over that period

100,000+

hours of manual analysis time Beyond says it has saved customers

Figures are Beyond's own, from its June 23, 2026 press release. The same release introduced Listing Lens, an AI listing analyzer, and framed the MCP server as supporting agent-to-agent workflows and BI hand-offs.

Prerequisites

A Beyond account with your listings synced. The MCP server surfaces your account's data, so an empty account gives Claude nothing to work with.
Beta access. Beyond's announcement says the MCP server is in beta and points interested operators to beyondpricing.com/str-developers.
Claude on the web, Claude Desktop, or Claude Code. 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 per account).
No Node.js, no terminal, no API key. This is the whole point.

Connect it: the walkthrough

Get on the beta

Visit beyondpricing.com/str-developers, the page Beyond's launch announcement directs operators to for MCP beta access and API documentation. If you have a Beyond customer success contact, asking them directly also works; the developer portal at developers.beyondpricing.com is public reading either way.

Add the custom connector in Claude

On claude.ai or Claude Desktop (Pro/Max, per Anthropic's help center):

Open Customize > Connectors in settings.
Click +, then Add custom connector.
Paste the server URL:

MCP server URL

https://neyoba.beyondpricing.com/mcp

Leave the advanced OAuth fields empty. Beyond supports dynamic client registration (RFC 7591), so Claude registers itself; there is no client ID to hunt down. On Team and Enterprise plans an organization owner adds the connector under Organization settings > Connectors first, then each member clicks Connect.

Sign in to Beyond and approve

Claude sends you to Beyond's consent page at v2.beyondpricing.com/oauth/authorize. Log in with your normal Beyond credentials and grant access. Under the hood this is the OAuth 2.0 Authorization Code flow with PKCE, scoped to neyoba:ask; Beyond's docs note that "most MCP clients automate all of this once you point them at the server URL." Claude never sees your password, only a scoped bearer token it can refresh.

Or: one command in Claude Code

If you live in the terminal, register the server with the Claude Code CLI instead:

Terminal

claude mcp add --transport http beyond https://neyoba.beyondpricing.com/mcp

Then run /mcp inside Claude Code to trigger the same browser-based Beyond sign-in.

Try it

"What Beyond tools do you have access to? Then list my listings with their current base price and tell me which one you'd look at first, and why."

Under the hood, for the curious

Beyond published the full OAuth endpoint map for the MCP server, which is more transparency than most vendors manage. You should never need to hardcode these (clients discover them from the metadata documents), but knowing what normal looks like helps when something breaks:

Purpose	URL
Protected-resource metadata (RFC 9728)	`https://neyoba.beyondpricing.com/.well-known/oauth-protected-resource/mcp`
Authorization-server metadata (RFC 8414)	`https://developers.beyondpricing.com/.well-known/oauth-authorization-server`
Dynamic client registration (RFC 7591)	`https://developers.beyondpricing.com/o/register/`
Authorization (sign-in / consent)	`https://v2.beyondpricing.com/oauth/authorize`
Token / refresh	`https://developers.beyondpricing.com/o/token/`
Revocation	`https://developers.beyondpricing.com/o/revoke/`

One nice detail from the docs: Beyond documents both client discovery paths, the spec-compliant one Claude uses (follow the protected-resource metadata's authorization_servers pointer) and the shortcut ChatGPT takes (read authorization-server metadata off the MCP server's own origin). Both land in the same flow.

Prefer raw API access? Beyond has that too

The MCP server sits on top of a real developer platform. Beyond's Partners API v1, documented at developers.beyondpricing.com, exposes Listings, Listing Customizations, Calendar, Compsets, Recommendations, Users, and Accounts endpoints, plus six signed webhook events (account created and refreshed, listing created, refreshed, base price changed, and in-active-market changed) so you can react to changes instead of polling.

Two authentication tracks:

Individual operators: a Personal Access Token, prefixed bpat_, created from the Beyond dashboard and shown exactly once. Send it as Authorization: Bearer bpat_... against /api/v1/ paths.
Partners and platforms: OAuth2 client credentials on a secure backend, following RFC 9700 guidance.

Beyond also publishes its OpenAPI spec and the entire documentation set as one markdown file specifically so AI coding agents can consume it, which tells you how seriously they are taking this audience. We took the same approach with the RapidEye API: pricing data and inspection intelligence are the two feeds an ops brain needs, and both should be a bearer token away.

Troubleshooting

The OAuth window opens but never completes

First check that you can log in to Beyond normally at v2.beyondpricing.com in the same browser; an expired session or SSO hiccup upstream will strand the consent page. Then remove the connector in Claude and add it again to restart the flow cleanly. Pop-up blockers are the other usual suspect, since the consent page opens in a browser window.

I can't get into the beta

Access runs through Beyond, not Anthropic. The launch announcement points operators to beyondpricing.com/str-developers. If that stalls, your Beyond account manager is the fastest route; the feature is a selling point for them right now.

Claude doesn't show any Beyond tools in the conversation

Check the connector shows as connected under Customize > Connectors, and re-authenticate if it shows an error state. In Claude Code, run /mcp and confirm the beyond server is listed and authenticated. On the Free plan, remember the one-custom-connector limit; a previously added connector may be occupying the slot.

How do I revoke access later?

Remove the connector in Claude's settings, which drops the client. Beyond's authorization server also implements a standard revocation endpoint (/o/revoke/), so tokens are killable server-side. If you went the REST route instead, delete the bpat_ personal access token from your Beyond dashboard.

Is this read-only? Can Claude change my prices?

Beyond does not publish the MCP server's tool list, and the single documented scope, neyoba:ask, frames access as assistant-style questioning rather than granular read/write grants. Until Beyond documents otherwise, treat the connection as live account access: let Claude analyze and draft, and confirm any pricing change yourself in the Beyond dashboard before it matters.

Frequently asked questions

Does Beyond have an official MCP server?

Yes. Announced June 23, 2026, in beta, and billed by Beyond as the first MCP server for revenue management. It connects AI tools including Claude and ChatGPT directly to Beyond's dynamic pricing data, and it is documented at developers.beyondpricing.com.

Do I need an API key to connect Beyond to Claude?

No. The MCP connection authenticates with OAuth: you sign in on Beyond's own page and approve. API keys (bpat_ personal access tokens) exist only for the REST API track.

What does the MCP server cost?

Beyond has not published separate pricing for the MCP beta; access is arranged through its str-developers page against your existing Beyond account. For contrast, PriceLabs bills its Customer API at $1 per synced listing per month.

What is Neyoba and why is it in the URL?

Neyoba is Beyond's in-app AI pricing assistant, launched late 2025 and used by 15,000+ hosts and property managers in its first six months, per Beyond. The MCP server runs at neyoba.beyondpricing.com and its OAuth scope is neyoba:ask, so the external AI access shares plumbing with the in-app assistant.

Does it work with ChatGPT and other AI tools?

Yes. Beyond's docs explicitly describe both Claude's spec-compliant discovery path and ChatGPT's variant, and the launch announcement names Claude, ChatGPT, and custom enterprise agents as supported clients.

Other guides

Dynamic pricing

Connect Beyond to Claude