Hipcamp MCP Server
Calendar, pricing and guest messages for hosts.
Hosted MCP Server
npx add-mcp 'https://cotlet.dev/mcp/v1/hipcamp'Installs into Claude Code, Codex, Cursor and more
Documentation
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Hipcamp API and MCP server: Let your AI agent answer Hipcamp campers on time.
Hipcamp has no MCP server and no public API. Its own llms.txt says it "does not document a public booking API" (checked 27 Oct 2026). Cotlet runs 15 Hipcamp tools hosted, over MCP for agents and REST for scripts, in your own host login.
Calendar, pricing and guest messages for hosts. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.
- Free 7-day trial, no card
- Unofficial, not affiliated with Hipcamp
- Page: https://cotlet.dev/integrations/hipcamp-api-mcp-server
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Hipcamp. Hipcamp is a trademark of its owner. If Hipcamp's own integrations cover what you need, use them first.
What can you automate in Hipcamp?
- Answer booking requests before they expire
- Reply to gate, firewood and pet questions
- Set weekend and event prices per site
- Close a site for reseeding or winter
- Draft replies to new reviews
- Report the week's bookings and payouts
Does Hipcamp have an MCP server or an API?
- Campgrounds on one of 16 partner systems, such as Cloudbeds, Newbook or Channex, can sync availability, prices and bookings. Hipcamp sets the link up itself, and those parks pay 12.5% commission instead of 15%.
- Every other host gets iCal sync, which moves availability only. There is no Zapier app and no n8n node.
- Nothing official reads or answers booking requests, camper messages, reviews or payouts.
| What you need | iCal sync | Partner PMS | Cotlet |
|---|---|---|---|
| Block or open dates | From another calendar | Yes | Yes, per site |
| Change nightly prices | No | Yes, on some systems | Yes, by weekday |
| Accept or decline requests | No | Not in the sync | Yes, after your OK |
| Camper messages and reviews | No | Not in the sync | Yes, after your OK |
| Who can use it | Any host | Parks on 16 partner systems | Any host |
| Price | Free | Your PMS plan | Pay per call |
Checked 27 Oct 2026. Sources: Hipcamp llms.txt, Hipcamp Help: Does Hipcamp integrate with my PMS?, Hipcamp Help: Hipcamp now integrates with Cloudbeds, Hipcamp Help: Listing cost and commission, Supergood: Hipcamp API report card
How does Cotlet connect to Hipcamp?
- Sign in to Hipcamp. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never keep your Hipcamp password, and no accept, decline, message or review reply reaches a camper before you approve it.
Connect Hipcamp to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Sign in to Hipcamp in a Cloud Browser. Make a Cotlet account, open Hipcamp in its Cloud Browser, log in to your own host account and press Enable for agents.
- Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 where your agent takes an MCP server or connector URL.
- Approve the connection. Chat apps send you to a Cotlet sign-in page. Code editors, n8n and scripts use an API key from the console.
Hipcamp shares https://cotlet.dev/mcp/v1 with every other app you enable on Cotlet. If you turn Hipcamp on after connecting, refresh the connector and its 15 tools appear.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: hipcamp_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: hipcamp_write
How to use the Hipcamp REST API
Create your Cotlet API key
Create a Cotlet API key with access to Hipcamp and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect Hipcamp in Cotlet and enable it for agents. Account access: Your own Hipcamp host account.
Make your first Hipcamp API request
REST:
curl https://cotlet.dev/api/v1/hipcamp/listings \
-H "Authorization: Bearer $COTLET_API_KEY"
Read listings and apply the operation limits
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "hipcamp",
"tool": "list_listings",
"result": {
"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"
}
]
}
]
}
}
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.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
Hipcamp workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Confirmed bookings in a date range with camper, site, dates, guests and total. Use list_bookings in your configured travel brief. |
| Make | HTTP > Make a request | One booking or request: camper, group size, message and price. Use get_booking in your configured travel brief. |
| Python or Node.js | REST API | Camper reviews of your listings with rating, text, date and your response. Use list_reviews in your configured travel brief. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads Hipcamp; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
Hipcamp API endpoints and MCP tools
Booking requests and bookings
A request expires 24 hours after it arrives, and a declined or expired one cannot be accepted later. Accepting charges the camper's held card. Request to Book is not offered to hosts in the UK and EU, so there these tools only read bookings.
- List booking requests (
list_booking_requests, read): Pending booking requests waiting for your answer, with dates, site and time left to respond. - Get booking (
get_booking, read): One booking or request: camper, group size, message and price. - Accept booking request (
accept_booking_request, write, asks first): Accept a pending booking request. The camper is notified and charged. - Decline booking request (
decline_booking_request, write, asks first): Decline a pending booking request. The camper is notified and not charged. - List bookings (
list_bookings, read): Confirmed bookings in a date range with camper, site, dates, guests and total.
Calendar and prices
A special price beats the base price and moves the extra-guest fee by the same percentage. Booked nights keep their price. Blocked dates keep the property in search.
- List listings (
list_listings, read): Your listings with their sites, status and base nightly price. - Get calendar (
get_calendar, read): Availability and nightly price per site and day, including blocked dates. - Update pricing (
update_pricing, write): Set a special nightly price for chosen nights. - Block dates (
block_dates, write): Make a site or a whole listing unavailable for a date range. - Unblock dates (
unblock_dates, write): Open blocked dates again for booking.
Inbox and reviews
A message in a pending thread does not count as an answer to the request. Review replies can be public under the review or private to the camper.
- List messages (
list_messages, read): Inbox conversations with campers, with the last message and its state. - Send message (
send_message, write, asks first): Send a message to a camper in an existing conversation. - List reviews (
list_reviews, read): Camper reviews of your listings with rating, text, date and your response. - Respond to review (
respond_to_review, write, asks first): Respond to a camper review, publicly or as a private message.
Payouts
US hosts are paid the Tuesday after checkout, so last weekend's stays may not be in a payout yet.
- List payouts (
list_payouts, read): Payouts with amount, status, date and the bookings they cover.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/hipcamp-api-mcp-server#tools
Who can see my Hipcamp session, and how do I revoke it?
- What we store. Your logged-in Hipcamp profile, AES-256-GCM encrypted, in Finland. No password.
- What your agent gets. The 15 Hipcamp tools, never the cookie.
- What the session sees. All your host account sees: campers, phone numbers, payouts.
- What no tool touches. Refunds, cancellations, payout settings, listing edits, Broadcasts.
- If Hipcamp logs you out. You log in again yourself, in the same Cloud Browser.
- How to cut access. Disable for agents, reset the browser or change your Hipcamp password.
Hipcamp has one login per host account and no co-host seats (help center, 15 Oct 2026), so the session can also open your payout and tax pages. No tool reads or changes them beyond the payout list. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Approvals, undo and mistakes
- Sorts by deadline. Pending requests, the one closest to its 24 hours first.
- Reads the camper's note. Group size, pets and arrival time against your site rules.
- Checks the nights. Still open on the calendar, or a decline is proposed instead.
- Waits for your OK. Each accept or decline sits in your Cotlet console with the time left.
| Action | Undo |
|---|---|
| Accept a request | No tool cancels; cancel in Hipcamp by hand, the camper was charged |
| Decline a request | No; the camper has to send a new request |
| Set a special price | Set the old price again; bookings made in between keep the new one |
| Block dates | unblock_dates opens them |
| Send a message or a review reply | No |
4 of 15 tools ask first: accept_booking_request, decline_booking_request, send_message and respond_to_review. Prices and blocked dates reach no camper directly and one call reverses them, so they run at once. You can switch the wait off per tool, for example for accepts that already match your rules.
An accept on your phone and one from the agent can cross. The agent reads the request again right before it acts, and a request that is gone fails at no cost.
MCP call:
{
"name": "update_pricing",
"arguments": {
"listing_id": "lst_48211",
"site_id": "site_meadow",
"from": "2027-07-01",
"to": "2027-07-31",
"nightly_price": 55,
"weekdays": [
"fri",
"sat"
]
}
}
REST:
curl -X PATCH https://cotlet.dev/api/v1/hipcamp/listings/lst_48211/pricing \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"site_id":"site_meadow","from":"2027-07-01","to":"2027-07-31","nightly_price":55,"weekdays":["fri","sat"]}'
Response:
{
"listing_id": "lst_48211",
"site_id": "site_meadow",
"nights_updated": 10,
"nightly_price": 55,
"currency": "USD"
}
The same tools answer over REST at /api/v1/hipcamp, with one key and one price, for example a cron job that sets next summer's Friday and Saturday prices every spring. A price for a site ID that does not exist returns an error, and failed calls are free. Each tool row above has its REST path.
How much does the Hipcamp MCP server cost?
About $24 a month for a farm with 3 tent sites in July, 4,100 credits. Listing on Hipcamp stays free; its 15% commission does not change.
| Job | Calls | Credits |
|---|---|---|
| Look for new booking requests, twice a day | 1 × 60 | 600 |
| Read, check and answer a request | 3 × 12 | 360 |
| Answer camper questions in the Inbox, daily | 4 × 30 | 1,200 |
| Weekend and event prices, weekly | 6 × 4 | 240 |
| Reply to new reviews, weekly | 3 × 4 | 120 |
| Bookings and payouts report, weekly | 2 × 4 | 80 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 4,100 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
The month is our example: about 20 two-night stays at $35 on Request to Book, 12 requests to screen, questions every day. Hipcamp puts a basic tent site at $20 to $40 a night and $3,000 to $10,000 a year, and publishes no booking counts. For scale, Hipcamp's 15% on that $1,400 of stays is $210. Dollars at the $29 pack rate.
Hipcamp MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| Cloudbeds and other partner PMSs | Two-way availability, prices and bookings for campgrounds, set up by Hipcamp. | Only on 16 partner systems, some on higher tiers; no requests, Inbox or reviews. |
| Apify Hipcamp scrapers | Public campsite listings, prices and reviews, pay per result. | Public pages only; they never log in to a host account. |
| Anakin Wire | 7 endpoints for hipcamp.com search, listing details and price breakdowns. | Camper-side data; no host actions. |
| Supergood | An unofficial API it builds per customer on the logged-in web app. | No public tool list or price; you talk to sales. |
We found no Hipcamp MCP server on GitHub, no Zapier app and no n8n node; the repos named Hipcamp are bootcamp clones of the website. A campground already on Cloudbeds or Newbook should use that link for availability and prices. For requests, the Inbox and reviews, Cotlet works in the host account you already run.
Who runs Cotlet
Cotlet belongs to Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Send questions about the Hipcamp tools to contact@cotlet.dev.
Hipcamp API and MCP: questions
How do I get access?
Sign up free at https://cotlet.dev, open Hipcamp under Integrations in the console and log in to Hipcamp in its Cloud Browser. The trial starts when you sign up and needs no card.
How do I connect Hipcamp to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Hipcamp once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Hipcamp account through Cotlet, in their phone apps too.
What can ChatGPT do in Hipcamp?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Hipcamp: respond to booking requests before they expire; set weekend, event and season prices; close the calendar for maintenance or the season. You ask in plain words, and anything that reaches other people waits for your OK first.
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 a co-host use it too?
Hipcamp has no co-host seats, so the agent works in the one host login. Your co-host can still answer in the Hipcamp app, and the agent reads the thread again before it replies, so it skips questions someone already answered.
Does it work for hosts in the UK and EU?
Yes, for prices, dates, the Inbox, reviews and payouts. Hipcamp offers Request to Book only outside the UK and EU, so there every stay is Instant Book and the request tools find nothing to answer.
Is the MCP server different from the REST API?
Only in how it is called. Both carry the same 15 tools, inputs, answers, API key and price. Agents use MCP; scripts and cron jobs use REST.
Is Cotlet affiliated with Hipcamp?
No. Cotlet is independent and not affiliated with Hipcamp Inc.
Can I use the Hipcamp API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.