Skip to main content
Glama
deenesjakoruzh
campertunity

Campertunity MCP Server

Official
by campertunity
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Campertunity AI 工具

用于在全球范围内搜索露营地、检查可用性并预订营位的 AI 工具。

包含 智能体技能文件 (agent skill files) 和一个用于 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

搜索半径（公里，默认：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