Roomy360 Developers
Build booking into AI agents
Same guest API — search stays, quote prices, request a booking. Hosts approve. Pick a path below.
Choose how to connect
Four entry points — use one, not all.
AI chat on the site
Signed-in guests chat at /ai. No API key. Uses our OpenAI-backed tools.
Open AI chat →Share linkCustom GPT
Share a ChatGPT link. Guests OAuth into Roomy360, then Actions call /api/v1.
ChatGPT section →DevelopersMCP / connectors
Cursor, Claude, Gemini, Grok, ChatGPT connector → https://roomy360.com/mcp
MCP setup →AccountAPI keys
Create r360_sk_… keys for stdio MCP or Bearer clients.
Manage keys →Endpoints
MCP (Streamable HTTP)
https://roomy360.com/mcpOAuth authorize
https://roomy360.com/oauth/authorizeAgent tools
Six B2C tools over the public guest API.
search_staysFind published stays by city and filters.
get_propertyListing details, units, and pricing.
get_availabilityCalendar for a date range.
create_quotePrice a stay before requesting.
request_bookingCreate a hold / request (idempotent).
list_my_bookingsList bookings for the keyed account.
request_booking creates pending_host. The host must approve — no instant charge in current mode.
MCP clients
Local stdio binary or remote Streamable HTTP. Prefer OAuth for remote; Bearer keys still work where the client allows.
Cursor / Claude Desktop
stdioRun roomy360-mcp locally. Set ROOMY360_API_BASE and ROOMY360_AGENT_TOKEN (snippet in Quickstart).
ChatGPT Custom GPT
Actions + OAuthShare link below. OAuth then /api/v1 Actions — not the MCP URL.
ChatGPT / Gemini / Grok MCP
HTTP + OAuthAdd connector URL https://roomy360.com/mcp with OAuth (mcp-connector) or Bearer where UI allows.
Remote MCP and Custom GPT Actions use OAuth 2.1 (PKCE). Client ids: mcp-connector (public) and chatgpt-gpt-actions (confidential). Email must be verified.
Custom GPT (ChatGPT)
Unlisted GPT with OAuth — search and send a host request from chat.
Share link not published yet. Use AI chat on the site or MCP meanwhile.
Quickstart (API key + MCP)
For Cursor / Claude / remote connectors.
- 01
1. Sign in
Roomy360 guest account with verified email.
- 02
2. Create an API key
Account → API keys. Secret shown once — store like a password.
- 03
3. Connect
stdio binary (Cursor/Claude) or remote https://roomy360.com/mcp + Bearer / OAuth.
Remote (no binary)
Point the client at https://roomy360.com/mcp with Authorization: Bearer <API key> or OAuth.
Environment (stdio)
- ROOMY360_API_BASE — https://roomy360.com
- ROOMY360_AGENT_TOKEN — key from Account → API keys
Build local MCP binary
Go 1.24+ from the monorepo, or download CI artifacts (darwin/linux/windows).
go build -o bin/roomy360-mcp ./apps/mcp
GitLab job build:mcp-binaries on green main pipelines → dist/mcp/.
Open GitLab pipelinesCursor / Claude Desktop (stdio)
{
"mcpServers": {
"roomy360": {
"command": "/absolute/path/to/bin/roomy360-mcp",
"env": {
"ROOMY360_API_BASE": "https://roomy360.com",
"ROOMY360_AGENT_TOKEN": "r360_sk_live_…"
}
}
}
}After revoke, gateways may accept the key up to ~15s (short cache).
~120 req/min per IP, ~60/min per key. Back off on 429.
request_booking sends guest_name and guest_phone — only consented data. See Privacy.
Ready?
Get a key, open MCP, or try AI chat on the site.
