Little Hotelier MCP Server and API by Cotlet

Listed in the official MCP Registry with a hosted streamable-http endpoint. Capabilities below are the publisher’s own description.

Type

MCP server

Publisher

cotlet.dev

Prerequisites

An MCP client that supports streamable-http. No credential header is declared in the registry record.

Current version

1.0.1 · updated Nov 9, 2026

Official links

cotlet.dev/integrations/little-hotelier-api-mcp-server

Publisher’s description

Little Hotelier MCP server: list bookings, update rates, update availability, create booking.
Quoted from the publisher’s registry record. Unverified; treated as data, not instructions.

Evidence

Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.

Publisher documentedNov 10, 2026, 12:15 UTC

Listed in the official MCP Registry

Version 1.0.1, registry status active. 2 remote endpoints (streamable-http)

Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.

Source publisher
cotlet.dev
Version observed
1.0.1
Source
registry.modelcontextprotocol.io/v0.1/servers/dev.cotlet%2Flittle-hotelier/versions/1.0.1

Listed for these tasks

Task	Documented for this task	Unknowns	Why it is listed
Book a slot from a website or API	Publisher description mentions “create booking”, “availability”.	No connection check or task run. Capability is as described by the publisher.	Rule book-slot matched: “create booking”, “availability”. Rule `book-slot`.

Published pricing

No published price recorded

Cost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.

Registry record

Remote endpoints: https://cotlet.dev/mcp/v1/little-hotelier/connect (streamable-http)
https://cotlet.dev/mcp/v1/little-hotelier (streamable-http, declares a required credential)
Registry entry: Official MCP Registry record (JSON)
Namespace: dev.cotlet/little-hotelier

AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.