Skip to main content
Glama
deenesjakoruzh
campertunity

Campertunity MCP Server

Official
by campertunity
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Campertunity AI 도구

전 세계 캠핑장을 검색하고, 예약 가능 여부를 확인하며, 캠핑장을 예약할 수 있는 AI 도구입니다.

AI 기반 캠핑장 탐색을 위한 에이전트 스킬 파일과 MCP 서버가 포함되어 있습니다.

에이전트 스킬 파일

이 패키지에는 OpenClaw, Claude Code, Codex 및 SKILL.md 형식을 지원하는 기타 에이전트 플랫폼과 호환되는 스킬 파일이 포함되어 있습니다.

스킬 설치:

# OpenClaw
openclaw skills install campertunity

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

Related MCP server: Currents

MCP 서버

빠른 시작

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

API 키 (선택 사항)

API 키는 필요하지 않습니다. 더 높은 속도 제한을 원하시면 campertunity.com/mcp에서 키를 받으세요:

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

사용 가능한 도구

listing-search

필터 및 위치 기반 검색을 사용하여 캠핑장을 검색합니다.

매개변수

유형

설명

limit

number

반환할 결과 수 (기본값: 50, 최대: 1000)

cursor

string

이전 응답의 페이지네이션 커서

startDate

string

예약 가능 시작 날짜 (YYYY-MM-DD)

endDate

string

예약 가능 종료 날짜 (YYYY-MM-DD)

adults

number

성인 수 (기본값: 1)

children

number

어린이 수 (기본값: 0)

latitude

number

중심점 위도

longitude

number

중심점 경도

radius

number

검색 반경 (km 단위, 기본값: 20)

region

string

지역/주 (위도/경도가 없는 경우 지오코딩됨)

city

string

도시 (위도/경도가 없는 경우 지오코딩됨)

country

string

국가 (위도/경도가 없는 경우 지오코딩됨)

countryCode

string

국가 코드, 예: "US", "CA"

filters

string[]

필터링할 태그 (아래 참조)

campgroundDescription

string

자연어 설명

listing-details

특정 리스팅에 대한 상세 정보를 가져옵니다.

매개변수

유형

설명

listingId

string

리스팅 ID

listing-availability

특정 날짜의 캠핑장 예약 가능 여부를 확인합니다.

매개변수

유형

설명

listingId

string

리스팅 ID

siteIds

string[]

선택적 특정 사이트 ID

startDate

string

시작 날짜 (YYYY-MM-DD)

endDate

string

종료 날짜 (YYYY-MM-DD)

listing-book

캠핑장 예약 URL을 가져옵니다.

매개변수

유형

설명

listingId

string

리스팅 ID

startDate

string

시작 날짜 (YYYY-MM-DD)

endDate

string

종료 날짜 (YYYY-MM-DD)

adults

number

성인 수 (기본값: 1)

children

number

어린이 수 (기본값: 0)

필터 태그

사이트 유형: tent, rv, lodging, glamping, cabin

접근성: driveIn, walkIn, equestrian, boat

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

편의 시설: picnicTable, fires, toilets, outhouse, potableWater, petFriendly, rvHookup, rvSanitation, trash, showers, wifi, handicap

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

데이터 공지

데이터는 여러 소스에서 수집되며 AI로 강화됩니다. 데이터를 재배포, 캐싱 또는 수정하지 마십시오. 항상 서버를 통해 실시간 데이터를 사용하십시오.

자세한 내용은 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