Skip to main content
Glama
deenesjakoruzh
campertunity

Campertunity MCP Server

Official
by campertunity
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Campertunity KI-Tools

KI-Tools zur Suche nach Campingplätzen, zur Überprüfung der Verfügbarkeit und zur Buchung von Stellplätzen auf der ganzen Welt.

Enthält Agent-Skill-Dateien und einen MCP-Server für KI-gestützte Campingplatzsuche.

Agent-Skill-Dateien

Dieses Paket enthält Skill-Dateien, die mit OpenClaw, Claude Code, Codex und anderen Agenten-Plattformen kompatibel sind, die das SKILL.md-Format unterstützen.

Installieren Sie den Skill:

# OpenClaw
openclaw skills install campertunity

# Claude Code / other platforms
# Copy skills/campertunity/SKILL.md to your workspace skills directory

Related MCP server: Currents

MCP-Server

Schnellstart

{
  "mcpServers": {
    "campertunity": {
      "command": "npx",
      "args": ["-y", "campertunity-ai-tools@latest"]
    }
  }
}

API-Schlüssel (optional)

Es ist kein API-Schlüssel erforderlich. Für höhere Ratenlimits erhalten Sie einen Schlüssel unter campertunity.com/mcp:

{
  "mcpServers": {
    "campertunity": {
      "command": "npx",
      "args": ["-y", "campertunity-ai-tools@latest"],
      "env": {
        "CAMPERTUNITY_API_KEY": "your_api_key_here"
      }
    }
  }
}

Verfügbare Tools

listing-search

Suche nach Campingplätzen mit Filtern und standortbasierter Suche.

Parameter

Typ

Beschreibung

limit

number

Anzahl der zurückzugebenden Ergebnisse (Standard: 50, max: 1000)

cursor

string

Paginierungs-Cursor aus der vorherigen Antwort

startDate

string

Startdatum der Verfügbarkeit (JJJJ-MM-TT)

endDate

string

Enddatum der Verfügbarkeit (JJJJ-MM-TT)

adults

number

Anzahl der Erwachsenen (Standard: 1)

children

number

Anzahl der Kinder (Standard: 0)

latitude

number

Breitengrad des Mittelpunkts

longitude

number

Längengrad des Mittelpunkts

radius

number

Suchradius in km (Standard: 20)

region

string

Region/Bundesland (geokodiert, falls kein Breitengrad/Längengrad angegeben)

city

string

Stadt (geokodiert, falls kein Breitengrad/Längengrad angegeben)

country

string

Land (geokodiert, falls kein Breitengrad/Längengrad angegeben)

countryCode

string

Ländercode, z. B. "US", "CA"

filters

string[]

Tags zum Filtern (siehe unten)

campgroundDescription

string

Beschreibung in natürlicher Sprache

listing-details

Erhalten Sie detaillierte Informationen zu einem bestimmten Eintrag.

Parameter

Typ

Beschreibung

listingId

string

ID des Eintrags

listing-availability

Überprüfen Sie die Verfügbarkeit von Stellplätzen für bestimmte Daten.

Parameter

Typ

Beschreibung

listingId

string

ID des Eintrags

siteIds

string[]

Optionale spezifische Stellplatz-IDs

startDate

string

Startdatum (JJJJ-MM-TT)

endDate

string

Enddatum (JJJJ-MM-TT)

listing-book

Erhalten Sie eine Buchungs-URL für einen Campingplatz.

Parameter

Typ

Beschreibung

listingId

string

ID des Eintrags

startDate

string

Startdatum (JJJJ-MM-TT)

endDate

string

Enddatum (JJJJ-MM-TT)

adults

number

Anzahl der Erwachsenen (Standard: 1)

children

number

Anzahl der Kinder (Standard: 0)

Filter-Tags

Stellplatztypen: tent, rv, lodging, glamping, cabin

Zugang: driveIn, walkIn, equestrian, boat

Aktivitäten: biking, boating, fishing, hiking, horsebackRiding, paddling, windSports, surfing, swimming, whitewaterPaddling, wildlifeWatching

Ausstattung: picnicTable, fires, toilets, outhouse, potableWater, petFriendly, rvHookup, rvSanitation, trash, showers, wifi, handicap

Gelände: beach, cave, desert, forest, hotSpring, lake, river, swimmingHole, waterfall, creek

Datenhinweis

Die Daten werden aus mehreren Quellen gesammelt und durch KI erweitert. Die Daten dürfen nicht weitergegeben, zwischengespeichert oder verändert werden. Verwenden Sie immer Echtzeitdaten über den Server.

Weitere Informationen finden Sie unter campertunity.com.

Available Tools

4 tools
place-availabilityD
ParametersJSON Schema
NameRequiredDescriptionDefault
placeIdYesThe id of the place to check availability for.
siteIdsNoThe ids of the sites to check availability for.
startDateYesThe start date to check availability for. Format: YYYY-MM-DD
endDateYesThe end date to check availability for. Format: YYYY-MM-DD

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

place-bookD
ParametersJSON Schema
NameRequiredDescriptionDefault
placeIdYesThe id of the place to book.
startDateNoThe start date of the booking. Format: YYYY-MM-DD
endDateNoThe end date of the booking. Format: YYYY-MM-DD
adultsNoNumber of adults. Default is 1.
childrenNoNumber of children. Default is 0.

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

place-detailsD
ParametersJSON Schema
NameRequiredDescriptionDefault
placeIdYesThe id of the place to get details for.

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 4 tool updates
    • First observedplace-availability
    • First observedplace-book
    • First observedplace-details
    • First observedplace-search
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.1/5.0
Disambiguation4/5

The tools have distinct purposes based on their names: search for finding places, details for getting information, availability for checking status, and book for making reservations. While the lack of descriptions introduces some ambiguity about exact boundaries, the core actions (search, get, check, reserve) are clearly differentiated.

Naming Consistency5/5

All tools follow a perfect 'place-verb' pattern with hyphenated naming (place-search, place-details, place-availability, place-book). This consistency makes the tool set predictable and easy to understand at a glance.

Tool Count5/5

With 4 tools, this server is well-scoped for a camping/place booking domain. Each tool covers a fundamental operation (search, view details, check availability, book), and there are no extraneous tools—each earns its place in the workflow.

Completeness4/5

The tool set covers the essential CRUD-like operations for a booking system: search (discover), details (read), availability (check), and book (create). A minor gap is the lack of update/cancel or delete operations for bookings, but agents can still complete core workflows with the provided tools.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/campertunity/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server