Skip to main content
API-first, not API-eventually

App Store, API & MCP

Every part of Camping.care is an app, and everything an app can do, your code can do. 134 integrations live, an open REST API, and an MCP server so AI platforms can work with your park directly.

For operators and for developers

Three ways in

  • The App Store

    134 apps covering channels, payments, statistics, fiscal compliance, accounting, access control and energy. Install what you need from inside your own environment.

    Browse the catalogue →
  • Open REST API

    The same API the platform itself runs on: reservations, guests, accommodations, rates, payments. Documented, versioned, with scopes so an app only gets what it needs.

    Read the documentation →
  • MCP server

    Point ChatGPT, Claude or Gemini at your park through the Model Context Protocol. Ask about occupancy, make a booking, look up a guest, with the permissions you grant, and no others.

    MCP documentation →
Otto

Building an integration?

Most of what you need is public. Read the App Store documentation first. A lot of requests turn out to be answered there.

App Store docs →

Why an open API matters for a campsite

An open API matters for a campsite for an unglamorous reason: you will eventually want to do something your software vendor has not thought of. A tour operator wants a feed. Your accountant wants the numbers in a particular shape. The energy meters you installed came from a supplier nobody has heard of.

With a closed system, each of those is a feature request that joins a queue. With an open API, it is an afternoon’s work for whoever builds your website.

Camping.care is built the same way it is sold: every part of the platform is an app talking to the same documented API, with scoped permissions. There are 134 integrations live today, and the ones that do not exist yet are buildable: by us, by a partner, or by you.

The MCP server is the newer half of this. It lets an AI assistant use your park’s data as a tool rather than as text: real availability, real reservations, real guests, within the permissions you grant. That is how Robin can answer a guest’s question about week 32 and be right.

Frequently asked about the API

Do I need permission to start building?

No. The documentation is public at starfish.care and you can build against a test environment straight away. You only need to talk to us when you want to publish an app in the App Store.

What can the API reach?

Reservations, guests, accommodations, rates, products, payments and the schedule board: the same surface the platform's own apps use. Access is scoped, so an app that only reads arrivals cannot touch payments.

What is MCP, in plain terms?

A standard way for AI assistants to use tools. With the MCP server connected, an assistant can answer "is a waterfront pitch free in week 32?" against your real availability instead of guessing, and (if you allow it) make the booking.

Is my data used to train anything?

No. Your park's data is yours. The AI agents work on your data to answer your questions; it is not training material.

How do I get my product listed?

Build it against the API, then send a partner request. We check the integration, agree how it is supported, and publish it. The partners page has the form.

DemoStart free