Coliving.com MCP Server v1.0.0

Coliving.com MCP Server

Search published monthly coliving listings, locations, availability, prices, and trust signals — plus personal bookings with lazy OAuth — using the Model Context Protocol.

Note: Listing discovery tools are public and read-only. Personal booking tools require OAuth only when called (lazy auth). No mutation or booking execution is exposed.

Connection Details

MCP Server URL https://mcp.coliving.com/mcp
Transport Type Streamable HTTP / Server-Sent Events (SSE)
Authentication Hybrid: public discovery tools (no token) + lazy OAuth for get_booking / list_bookings
Version 1.0.0
Health https://mcp.coliving.com/health
Connector Manifest https://mcp.coliving.com/connector.json
Status Production Active

Changelog

v1.0.0 2026-07-31
  • Expanded public discovery tools: get_host, compare_listings, recommend_listings, search_reviews, check_availability, search_amenities.
  • Hybrid OAuth for personal bookings: get_booking, list_bookings (scopes mcp:use, bookings:read).
  • Public listing tools remain anonymous; OAuth is lazy (only when calling protected tools).
v1.0.0 2026-07-01
  • Initial public read-only MCP server for listing discovery.
  • Tools: search_listings, get_listing, search_locations, get_filter_options.
  • Human-friendly amenity and community filter normalization.

Safety and Policy

  • Listing discovery tools are read-only and anonymous. No resource mutation or booking execution is allowed.
  • Personal booking tools (get_booking, list_bookings) use lazy OAuth with scopes mcp:use and bookings:read.
  • Only published and active listings are indexed and searchable.
  • Prices, discounts, and real-time availability may vary; agents must direct users to canonical listing URLs for final booking.
  • Rate limit: 120 requests per minute per IP address.
  • Request metadata (tool name, latency, IP, user-agent) is logged for reliability and security auditing. No personal data is retained.
  • Security contact: security@coliving.com