MCP server

Connect any MCP-compatible agent to the B2A travel decision engine.

Six tools that let any MCP-aware agent search stays, resolve destinations, and hand off bookings — no custom HTTP plumbing.

Connection URL

https://mcp.b2a.bluepillow.com/

Transport: streamable-HTTP (the default for hosted MCP servers).

Authentication

Same bearer key as the REST API. Pass it via Authorization: Bearer pk_…. If your agent has no key configured, call the b2a_get_key tool first — it issues an anonymous key on the fly.

Quick connect

Claude Code

claude mcp add b2a https://mcp.b2a.bluepillow.com/ \
  --header "Authorization: Bearer <your-key>"

Cursor

{
  "mcpServers": {
    "b2a": {
      "url": "https://mcp.b2a.bluepillow.com/",
      "headers": { "Authorization": "Bearer <your-key>" }
    }
  }
}

Per-stack guides: Agent quickstart.

Tools

Full reference at /docs/mcp/tools. Summary:

• b2a_get_key — issue an anonymous bearer key.
• resolve_destination — place name → destination id.
• discover_destinations_near — destinations within a radius.
• search_stays — ranked discovery search.
• get_property_details — canonical property record.
• check_property_availability — live availability + offers.