Duplex 77 availability

A public, read-only MCP server for the holiday lets in Céret — v0.2.0

It answers one question: which nights are free? for Duplex 77 (duplex), the whole duplex apartment in the centre of Céret, with terrace, let as one unit. It knows nothing about who booked, where, or prices.

Endpoint

https://mcp.duplex77.fr/mcp — Streamable HTTP, no authentication.
https://mcp.duplex77.fr/health — liveness check.

The same server, same-origin on the booking site:

Discovery: /.well-known/mcp/server-card.json on every one of those hosts (this host's card). All of this site's APIs — this server, the availability API and the concierge agent — are listed in the RFC 9727 API catalog at duplex77.fr/.well-known/api-catalog. An Agent Skill explaining all three is indexed at duplex77.fr/.well-known/agent-skills/index.json (SKILL.md).

Add it to Claude

Claude Code:

claude mcp add --transport http duplex-77 https://mcp.duplex77.fr/mcp

Claude Desktop / claude.ai: Settings → Connectors → Add custom connector → https://mcp.duplex77.fr/mcp. Or in claude_desktop_config.json:

{
  "mcpServers": {
    "duplex-77": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.duplex77.fr/mcp"
      ]
    }
  }
}

Tools

list_units
The unit: id, name, description, sleeps, bedrooms.
check_availability { unit, checkin, checkout }
Is the unit free for that stay? Nights and any conflicting blocked ranges.
get_availability { from?, to?, units? }
Blocked ranges per unit (default: the next 365 days, max 731).
find_free_stays { unit, nights, from?, to? }
The first 20 possible stays of exactly that many nights, plus the free periods they fall in.

Dates are YYYY-MM-DD; ranges are half-open [checkin, checkout), so you can arrive on someone else's departure day. Unit ids: duplex. Data comes from the public API at api.duplex77.fr and is up to a few minutes old. To book, go to duplex77.fr.