Skip to main content
Glama
deenesjakoruzh
campertunity

Campertunity MCP Server

Official
by campertunity
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Herramientas de IA de Campertunity

Herramientas de IA para buscar campings, comprobar disponibilidad y reservar parcelas en todo el mundo.

Incluye archivos de habilidades de agente y un servidor MCP para el descubrimiento de campings mediante IA.

Archivos de habilidades de agente

Este paquete incluye archivos de habilidades compatibles con OpenClaw, Claude Code, Codex y otras plataformas de agentes que admiten el formato SKILL.md.

Instalar la habilidad:

# OpenClaw
openclaw skills install campertunity

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

Related MCP server: Currents

Servidor MCP

Inicio rápido

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

Clave de API (opcional)

No se requiere ninguna clave de API. Para obtener límites de tasa más altos, obtenga una clave en campertunity.com/mcp:

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

Herramientas disponibles

listing-search

Busque campings con filtros y búsqueda basada en la ubicación.

Parámetro

Tipo

Descripción

limit

number

Resultados a devolver (predeterminado: 50, máx: 1000)

cursor

string

Cursor de paginación de la respuesta anterior

startDate

string

Fecha de inicio de disponibilidad (AAAA-MM-DD)

endDate

string

Fecha de fin de disponibilidad (AAAA-MM-DD)

adults

number

Número de adultos (predeterminado: 1)

children

number

Número de niños (predeterminado: 0)

latitude

number

Latitud del punto central

longitude

number

Longitud del punto central

radius

number

Radio de búsqueda en km (predeterminado: 20)

region

string

Región/estado (geocodificado si no hay lat/lng)

city

string

Ciudad (geocodificada si no hay lat/lng)

country

string

País (geocodificado si no hay lat/lng)

countryCode

string

Código de país, p. ej. "US", "CA"

filters

string[]

Etiquetas para filtrar (ver abajo)

campgroundDescription

string

Descripción en lenguaje natural

listing-details

Obtenga información detallada sobre un listado específico.

Parámetro

Tipo

Descripción

listingId

string

ID del listado

listing-availability

Compruebe la disponibilidad de parcelas para fechas específicas.

Parámetro

Tipo

Descripción

listingId

string

ID del listado

siteIds

string[]

IDs de parcelas específicas opcionales

startDate

string

Fecha de inicio (AAAA-MM-DD)

endDate

string

Fecha de fin (AAAA-MM-DD)

listing-book

Obtenga una URL de reserva para un camping.

Parámetro

Tipo

Descripción

listingId

string

ID del listado

startDate

string

Fecha de inicio (AAAA-MM-DD)

endDate

string

Fecha de fin (AAAA-MM-DD)

adults

number

Número de adultos (predeterminado: 1)

children

number

Número de niños (predeterminado: 0)

Etiquetas de filtro

Tipos de sitio: tent, rv, lodging, glamping, cabin

Acceso: driveIn, walkIn, equestrian, boat

Actividades: biking, boating, fishing, hiking, horsebackRiding, paddling, windSports, surfing, swimming, whitewaterPaddling, wildlifeWatching

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

Terreno: beach, cave, desert, forest, hotSpring, lake, river, swimmingHole, waterfall, creek

Aviso sobre los datos

Los datos se recopilan de múltiples fuentes y se mejoran con IA. No redistribuya, almacene en caché ni modifique los datos. Utilice siempre datos en tiempo real a través del servidor.

Para obtener más información, visite 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