# Hipcamp API and MCP server

> Hipcamp has no public API (checked 11 Oct 2026). Its own agent file says it does not document a public booking API. Hosts connect through iCal calendar sync, which shares availability, or through partner property management systems that Hipcamp integrates with directly.

Marketplace for camping on private land, campgrounds, RV parks and glamping, where hosts list sites and campers book them.

## What is the Hipcamp API?

Cotlet's Hipcamp API exposes 15 endpoints for your own Hipcamp account: list listings, list bookings, list booking requests, get booking, get calendar, list messages, list reviews, list payouts, block dates, unblock dates, update pricing, accept booking request, decline booking request, send message and respond to review. The list_listings endpoint returns your listings with their sites, status and base nightly price. Each endpoint takes simple JSON inputs like listing_id, from or to and works both as an MCP tool for agents and as a REST call for scripts.

- **Category:** [Travel](https://cotlet.dev/integrations/category/travel)
- **Endpoints:** 15 (8 read, 7 write)
- **Updated:** 2026-10-11

Hipcamp has no public API (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Hipcamp with 15 endpoints (8 read, 7 write): your AI agent signs in as you and does the work.

## Does Hipcamp have an official API?

Hipcamp has no public API (checked 11 Oct 2026). Its own agent file says it does not document a public booking API. Hosts connect through iCal calendar sync, which shares availability, or through partner property management systems that Hipcamp integrates with directly.

| Task | Hipcamp official | Cotlet |
|---|---|---|
| List bookings and booking requests | Partly: Only inside a partner PMS | Yes |
| Accept or decline booking requests | No: Email, Inbox, app or text message by hand | Yes |
| Block or open dates | Partly: iCal sync or a partner PMS | Yes |
| Change nightly prices | No: By hand in Calendar > Bulk Edit; PMS prices do not carry over | Yes |
| Read and reply to guest messages | No | Yes |
| Respond to reviews | No | Yes |
| List payouts | No: Payouts tab and a downloadable report by hand | Yes |

Sources: [Hipcamp: Become a Host (calendar syncing, PMS integrations)](https://www.hipcamp.com/en-US/host), [Hipcamp llms.txt: no public booking API](https://www.hipcamp.com/llms.txt), [Hipcamp Help: Does Hipcamp integrate with my reservation system or PMS?](https://support.hipcamp.com/hc/en-us/articles/19016296707220-Does-Hipcamp-integrate-with-my-reservation-system-or-property-management-system), [Hipcamp Help: Accepting or Declining a Booking Request](https://support.hipcamp.com/hc/en-us/articles/360024823132-Accepting-or-Declining-a-Booking-Request), [Hipcamp Help: Setting up your Calendar and Pricing for 2026](https://support.hipcamp.com/hc/en-us/articles/43460053251988-Setting-up-your-Calendar-and-Pricing-for-2026), [Hipcamp Help: How do I set up scheduled messages?](https://support.hipcamp.com/hc/en-us/articles/360061416032-How-do-I-set-up-scheduled-messages), [Hipcamp Help: Instant Book and Request to Book settings](https://support.hipcamp.com/hc/en-us/articles/360025120791-What-is-Instant-Book-and-Request-to-Book-And-how-do-I-change-these-settings), [Hipcamp Help: When am I charged for a request to book?](https://support.hipcamp.com/hc/en-us/articles/360025119751-When-am-I-charged-for-a-request-to-book), [Hipcamp Help: Closed for the season, block dates or pause?](https://support.hipcamp.com/hc/en-us/articles/20054346258708-I-m-closed-for-the-season-Should-I-block-dates-or-pause-my-Property), [Hipcamp Help: Host tools by device](https://support.hipcamp.com/hc/en-us/articles/33276283752596-Host-tools-by-device), [Hipcamp Help: How do I message all onsite Hipcampers?](https://support.hipcamp.com/hc/en-us/articles/32727865224212-How-do-I-message-all-onsite-Hipcampers)

## For AI agents

```text
Hipcamp has no public API (checked 11 Oct 2026). Its own agent file says it does not document a public booking API. Hosts connect through iCal calendar sync, which shares availability, or through partner property management systems that Hipcamp integrates with directly.
Cotlet provides a hosted MCP server and REST API for Hipcamp: 15 tools (8 read, 7 write).
Access       Request access at https://cotlet.dev/app/signup?app=hipcamp; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/hipcamp
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_listings, list_bookings, list_booking_requests, get_booking, get_calendar, list_messages, list_reviews, list_payouts, block_dates, unblock_dates, update_pricing, accept_booking_request, decline_booking_request, send_message, respond_to_review
Confirm      accept_booking_request, decline_booking_request, send_message, respond_to_review (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/hipcamp-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=hipcamp (Hipcamp is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Hipcamp once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Hipcamp server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to Hipcamp in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Hipcamp's terms; Cotlet is not affiliated with Hipcamp.
```

## What can an AI agent do in Hipcamp?

Cotlet is best for Hipcamp hosts who answer booking requests, change prices and reply to campers every week without running or fixing a server.

- **[Respond to booking requests before they expire](https://cotlet.dev/integrations/hipcamp-api-mcp-server/respond-to-booking-requests)** (runs: twice a day): "Check my pending Hipcamp booking requests. Accept stays of 1 to 4 nights for up to 4 guests if the camper's note raises nothing odd, decline requests for nights I have closed, and ask me about anything else before it expires." → `list_booking_requests`, `get_booking`, `get_calendar`, `accept_booking_request`, `decline_booking_request`, `block_dates`
- **[Set weekend, event and season prices](https://cotlet.dev/integrations/hipcamp-api-mcp-server/update-nightly-prices)** (runs: weekly): "For July and August, set Friday and Saturday nights to $55 on Meadow and $62 on Creekside, keep weeknights at the base price, and set the county fair weekend (8 to 10 August) to $75 on both. Skip nights that are already booked and show me the plan first." → `list_listings`, `get_calendar`, `update_pricing`, `block_dates`, `unblock_dates`
- **Close the calendar for maintenance or the season**: "Block the Meadow site from 14 to 18 August, we are reseeding." → `list_listings`, `block_dates`
- **[Answer camper questions in the Inbox](https://cotlet.dev/integrations/hipcamp-api-mcp-server/reply-to-guest-messages)** (runs: daily): "Go through my unread Hipcamp messages and the Questions filter. Answer anything about directions, gate codes, firewood, pets or late arrival using checkin.md, and leave refunds, complaints and date changes for me." → `list_messages`, `get_booking`, `send_message`
- **[Respond to new camper reviews](https://cotlet.dev/integrations/hipcamp-api-mcp-server/respond-to-reviews)** (runs: weekly): "Every Monday, list Hipcamp reviews from the last 14 days that I have not answered. Draft a private thank-you for short positive ones and a public reply for anything that mentions a problem, and show me the drafts first." → `list_reviews`, `get_booking`, `respond_to_review`
- **Weekly bookings and payouts report** (runs: weekly): "Every Monday, send me last week's bookings and payouts." → `list_bookings`, `list_payouts`

## Can Hipcamp automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Hipcamp connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to respond to booking requests before they expire, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/hipcamp/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/hipcamp/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/hipcamp/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/hipcamp/{tool} with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 15 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 403 until the account has an API key with access to Hipcamp.

### list_listings

Your listings with their sites, status and base nightly price. Access: read. REST: `POST /api/v1/hipcamp/list_listings`.

No parameters.

Returns every listing in your host account with its sites. Use listing_id and site_id from each item in the other endpoints. Base price is the price on the site, before any special price you set on single nights.

Example response:

```json
{
  "listings": [
    {
      "listing_id": "lst_48211",
      "name": "Willow Creek Farm",
      "status": "live",
      "sites": [
        {
          "site_id": "site_meadow",
          "name": "Meadow",
          "base_price": 45,
          "currency": "USD"
        },
        {
          "site_id": "site_creek",
          "name": "Creekside",
          "base_price": 52,
          "currency": "USD"
        }
      ]
    }
  ]
}
```

### list_bookings

Confirmed bookings in a date range with camper, site, dates, guests and total. Access: read. REST: `POST /api/v1/hipcamp/list_bookings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | date | no | First arrival date. Default: today. |
| `to` | date | no | Last arrival date. Default: 30 days from today. |
| `listing_id` | string | no | Only this listing. |
| `status` | enum | no | upcoming, current, past or cancelled. Default: upcoming. |

Lists confirmed bookings whose arrival falls in the range, soonest arrival first. Booking requests still waiting for your answer are not included; list_booking_requests returns those. Total is what the camper paid for the stay.

Example response:

```json
{
  "bookings": [
    {
      "booking_id": "bk_90105",
      "listing_id": "lst_48211",
      "site": "Meadow",
      "camper": "Maya R.",
      "arrival": "2026-10-16",
      "departure": "2026-10-18",
      "guests": 3,
      "total": 90,
      "currency": "USD",
      "status": "upcoming"
    }
  ]
}
```

### list_booking_requests

Pending booking requests waiting for your answer, with dates, site and time left to respond. Access: read. REST: `POST /api/v1/hipcamp/list_booking_requests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | no | Only this listing. |

Lists requests to book that you have not accepted or declined, soonest expiry first. A request expires 24 hours after it arrives if you do not respond, and expires_at shows when. Pass booking_id to get_booking, accept_booking_request or decline_booking_request.

Example response:

```json
{
  "requests": [
    {
      "booking_id": "bk_90217",
      "listing_id": "lst_48211",
      "site": "Meadow",
      "camper": "Jon P.",
      "arrival": "2026-10-23",
      "departure": "2026-10-25",
      "guests": 2,
      "expires_at": "2026-10-12T09:14:00Z"
    }
  ]
}
```

### get_booking

One booking or request: camper, group size, message and price. Access: read. REST: `POST /api/v1/hipcamp/get_booking`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `booking_id` | string | yes | Booking ID from list_bookings or list_booking_requests. |

Returns one booking or booking request with the camper's first name, number of guests, the message they sent with the request and the price for the stay. Use it before accepting so your agent reads the camper's note.

Example response:

```json
{
  "booking_id": "bk_90217",
  "status": "pending_request",
  "site": "Meadow",
  "camper": "Jon P.",
  "arrival": "2026-10-23",
  "departure": "2026-10-25",
  "guests": 2,
  "camper_message": "Two adults and a dog, arriving after 5 pm.",
  "nights": 2,
  "nightly_price": 45,
  "total": 90,
  "currency": "USD"
}
```

### get_calendar

Availability and nightly price per site and day, including blocked dates. Access: read. REST: `POST /api/v1/hipcamp/get_calendar`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from list_listings. |
| `site_id` | string | no | One site of the listing. Default: all sites. |
| `from` | date | yes | First day. |
| `to` | date | yes | Last day. |

Returns one row per site and night with its price and state: available, booked or blocked. Special prices are shown as set; days without one show the base price. Use it before update_pricing to see what a change would touch.

Example response:

```json
{
  "site_id": "site_meadow",
  "days": [
    {
      "date": "2027-07-02",
      "state": "available",
      "nightly_price": 45,
      "special_price": false
    },
    {
      "date": "2027-07-03",
      "state": "booked",
      "nightly_price": 45,
      "special_price": false
    },
    {
      "date": "2027-07-04",
      "state": "blocked",
      "nightly_price": 45,
      "special_price": false
    }
  ]
}
```

### list_messages

Inbox conversations with campers, with the last message and its state. Access: read. REST: `POST /api/v1/hipcamp/list_messages`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `filter` | enum | no | unread, pending, future, past or questions. Default: unread. |
| `booking_id` | string | no | Only the conversation of this booking. |

Lists Inbox conversations, most recent first, with the same filters as the Inbox. Pending conversations include booking requests waiting for your answer. Use conversation_id in send_message.

Example response:

```json
{
  "conversations": [
    {
      "conversation_id": "cv_33170",
      "camper": "Maya R.",
      "booking_id": "bk_90105",
      "last_message": "Which gate is the Meadow site? We arrive Friday.",
      "last_message_at": "2026-10-11T08:02:00Z",
      "unread": true
    }
  ]
}
```

### list_reviews

Camper reviews of your listings with rating, text, date and your response. Access: read. REST: `POST /api/v1/hipcamp/list_reviews`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | no | Only this listing. |
| `since` | date | no | Only reviews on or after this date. |
| `responded` | boolean | no | false: only reviews without your response. |

Lists reviews newest first, each with your public response if you wrote one. Leave responded empty to get all of them, or set it to false to find reviews you have not answered.

Example response:

```json
{
  "reviews": [
    {
      "review_id": "rv_5521",
      "listing_id": "lst_48211",
      "camper": "Maya R.",
      "recommended": true,
      "text": "Quiet site, great creek, easy host.",
      "created_at": "2026-10-08T14:30:00Z",
      "response": null
    }
  ]
}
```

### list_payouts

Payouts with amount, status, date and the bookings they cover. Access: read. REST: `POST /api/v1/hipcamp/list_payouts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `since` | date | no | Only payouts on or after this date. Default: 90 days ago. |

Lists payouts as the Payouts tab shows them, newest first, each with the bookings it covers. A booking is paid after the camper checks out, so recent stays can still be missing.

Example response:

```json
{
  "payouts": [
    {
      "payout_id": "po_7731",
      "date": "2026-10-06",
      "amount": 170,
      "currency": "USD",
      "status": "paid",
      "bookings": [
        "bk_89990",
        "bk_90012"
      ]
    }
  ]
}
```

### block_dates

Make a site or a whole listing unavailable for a date range. Access: write. REST: `POST /api/v1/hipcamp/block_dates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from list_listings. |
| `site_id` | string | no | One site of the listing. Default: all sites. |
| `from` | date | yes | First blocked night. |
| `to` | date | yes | Last blocked night. |
| `reason` | string | no | Closure reason, as offered in Bulk Edit. |

Turns off availability for the nights in the range, the same as Bulk Edit in the Calendar. Blocking keeps the property in Hipcamp search. It reaches no one and unblock_dates undoes it, so it runs without asking.

Example response:

```json
{
  "listing_id": "lst_48211",
  "site_id": "site_meadow",
  "from": "2027-08-14",
  "to": "2027-08-18",
  "reason": "Maintenance",
  "nights_blocked": 5
}
```

### unblock_dates

Open blocked dates again for booking. Access: write. REST: `POST /api/v1/hipcamp/unblock_dates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from list_listings. |
| `site_id` | string | no | One site of the listing. Default: all sites. |
| `from` | date | yes | First night to open. |
| `to` | date | yes | Last night to open. |

Turns availability back on for the nights in the range. It reaches no one and block_dates undoes it, so it runs without asking.

Example response:

```json
{
  "listing_id": "lst_48211",
  "site_id": "site_meadow",
  "from": "2027-08-14",
  "to": "2027-08-18",
  "nights_opened": 5
}
```

### update_pricing

Set a special nightly price for chosen nights. Access: write. REST: `POST /api/v1/hipcamp/update_pricing`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from list_listings. |
| `site_id` | string | no | One site of the listing. Default: all sites. |
| `from` | date | yes | First night. |
| `to` | date | yes | Last night. |
| `nightly_price` | integer | yes | Price per night in the listing currency, whole units. |
| `weekdays` | string[] | no | Only these days: mon, tue, wed, thu, fri, sat, sun. Default: every day. |

Sets a special price for the nights in the range, the same as Bulk Edit in the Calendar. A special price takes precedence over the base price and applies to bookings made after the change; confirmed bookings keep their price. It reaches no one directly and one call undoes it, so it runs without asking.

Example response:

```json
{
  "listing_id": "lst_48211",
  "site_id": "site_meadow",
  "nights_updated": 10,
  "nightly_price": 55,
  "currency": "USD"
}
```

### accept_booking_request

Accept a pending booking request. The camper is notified and charged. Access: write, asks the user first. REST: `POST /api/v1/hipcamp/accept_booking_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `booking_id` | string | yes | Booking ID from list_bookings or list_booking_requests. |
| `message` | string | no | Optional note to the camper. |

Accepts the request; Hipcamp then captures the charge it held when the request came in, and the camper is notified. Only requests that have not expired can be accepted. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "booking_id": "bk_90217",
  "status": "confirmed",
  "site": "Meadow",
  "arrival": "2026-10-23",
  "departure": "2026-10-25",
  "total": 90,
  "currency": "USD"
}
```

### decline_booking_request

Decline a pending booking request. The camper is notified and not charged. Access: write, asks the user first. REST: `POST /api/v1/hipcamp/decline_booking_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `booking_id` | string | yes | Booking ID from list_bookings or list_booking_requests. |
| `message` | string | no | Optional note to the camper explaining why. |

Declines the request and notifies the camper. The camper is not charged. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "booking_id": "bk_90218",
  "status": "declined",
  "camper_charged": false
}
```

### send_message

Send a message to a camper in an existing conversation. Access: write, asks the user first. REST: `POST /api/v1/hipcamp/send_message`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | string | yes | Conversation ID from list_messages. |
| `body` | string | yes | Message text. |

Posts a message in an Inbox conversation under your host name and returns its ID. Start from a conversation_id returned by list_messages. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "conversation_id": "cv_33170",
  "message_id": "msg_88410",
  "sent_at": "2026-10-11T09:05:00Z"
}
```

### respond_to_review

Respond to a camper review, publicly or as a private message. Access: write, asks the user first. REST: `POST /api/v1/hipcamp/respond_to_review`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `review_id` | string | yes | Review ID from list_reviews. |
| `body` | string | yes | Response text. |
| `visibility` | enum | no | public or private. Default: public. |

Posts your response under the review, or sends it to the camper as a private message. A public response appears under your name for future campers. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "review_id": "rv_5521",
  "visibility": "public",
  "posted_at": "2026-10-11T09:12:00Z"
}
```

## How do I connect Hipcamp to Claude Code, Codex or Cursor?

Connecting Hipcamp takes three steps: request access, sign in to Hipcamp once, then add one MCP server or call the REST API with the same key.

### Connect Hipcamp to your agent.

1. **Create an account** Sign up and add Hipcamp in the console. Your API key is there too.

2. **Sign in to Hipcamp once** Open the connect page from the console and sign in to Hipcamp the way you always do. We keep the session, never your password, and you can revoke it anytime.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Hipcamp tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Check my pending Hipcamp booking requests. Accept stays of 1 to 4 nights for up to 4 guests if the camper's note raises nothing odd, decline requests for nights I have closed, and ask me about anything else before it expires.
```

### Call Hipcamp from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is a POST endpoint at /api/v1/hipcamp/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/hipcamp/update_pricing \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"listing_id":"lst_48211","site_id":"site_meadow","from":"2027-07-01","to":"2027-07-31","nightly_price":55,"weekdays":["fri","sat"]}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "listing_id": "lst_48211",
  "site_id": "site_meadow",
  "nights_updated": 10,
  "nightly_price": 55,
  "currency": "USD"
}
```

## Why use Cotlet for Hipcamp?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Hipcamp yourself. We keep only the session, encrypted with AES-256.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Pick read only, or read and write.
- Anything that reaches other people waits for your OK, unless you switch it off per tool.
- Revoke access in one click.

**Kept working for you**

- We test every integration daily.
- When Hipcamp changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is there a Hipcamp MCP server on GitHub?

No Hipcamp MCP server exists. The realistic options are iCal calendar sync, which shares availability only, a partner PMS, or doing it by hand in the Hipcamp dashboard. Scrapers read public listings and cannot sign in to your host account.

|  | Calendar sync or PMS | Cotlet |
|---|---|---|
| Setup | Copy iCal links between Hipcamp and the other platform, or move your listing into a partner PMS | Request access, sign in to Hipcamp once, add one MCP server or API key |
| What it covers | iCal: availability. PMS: availability and bookings; prices are set in Hipcamp by hand | Bookings, booking requests, calendar, prices, messages, reviews and payouts |
| Messages and reviews | Not covered | Read and reply, each reply confirmed by you |
| When Hipcamp changes | Hipcamp and the partner maintain the link | Our team tests it daily and fixes it for you; failed calls are free |
| Your Hipcamp session | Not needed | Encrypted in an EU vault, limited to the actions you allow, revoked in one click |
| Where it runs | Inside the other platform or PMS | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | iCal is free; a PMS has its own plan | Free 7-day trial with 5,000 credits, then credits per call |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Hipcamp changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want the session to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Hipcamp API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Hipcamp API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

| Size | Price | Credits / month | Per credit |
|---|---|---|---|
| Solo | $29/mo | 3,000 | about $0.0097 |
| Pro | $99/mo | 12,000 | about $0.0083 |
| Agency | $299/mo | 40,000 | $0.0075 |

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Hipcamp account.

- **Company details:** The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. [Terms](https://cotlet.dev/terms)
- **Your session:** You sign in to Hipcamp yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Hipcamp tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect Hipcamp in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Hipcamp's terms:** You use your own Hipcamp account and stay responsible for following Hipcamp's terms. Cotlet is independent and not affiliated with Hipcamp. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Request access and pick Hipcamp. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to Hipcamp once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is a hosted server safe? My Hipcamp session would leave my computer.**

Cotlet keeps your Hipcamp session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

**Does Hipcamp allow automation of a host account?**

Hipcamp's Terms of Use ban scrapers and automated software that pull data from its pages, and say you may not share your account or password with anyone. Cotlet never stores your password and acts only in your own session; whether that fits the Terms is for you to decide before you request access.

**Do calendar sync and Cotlet work together?**

Yes. iCal sync keeps availability in step with other platforms, and Hipcamp syncs calendars right before a new booking goes through. Cotlet handles what iCal does not carry: prices, requests, messages and reviews. Calendar sync works only on live listings.

**Can my agent post or send messages in Hipcamp without asking me?**

No. Every call to accept_booking_request, decline_booking_request, send_message or respond_to_review waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. block_dates, unblock_dates, update_pricing runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Hipcamp API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/hipcamp/{tool} from the HTTP Request node.