Campspot MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CAMPSPOT_API_KEY | Yes | API key for Campspot API, obtain from Campspot support | |
| CAMPSPOT_BASE_URL | No | Base URL for Campspot API (optional, override for sandbox or per-park URL) | https://api.campspot.com |
| CAMPSPOT_AUDIT_LOG | No | Path to audit log file (optional, defaults to stderr) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Verify credentials work. If this fails, all other tools will too. Use when: starting a session, debugging auth, or after rotating
CAMPSPOT_API_KEY. Calls |
| list_sitesA | List campsites at the configured park. Use when: "what sites do I have?", "show me the first 20 sites",
"what's the offset for the next page?". Returns the API's native page
shape — dict with Example: limit=50, offset=0 — first page of 50 sites. |
| get_siteA | Get details for a single campsite by id. Use when: "tell me about site 42", "what's the max occupancy of site 17?". Returns the full site record (name, type, capacity, rates). |
| search_availabilityA | Find campsites available across a date range. Use when: "is there anything open July 4-7?", "what's free next weekend?", "which of these sites is available Aug 1-5?". Args: start_date: ISO date YYYY-MM-DD (inclusive) end_date: ISO date YYYY-MM-DD (exclusive — night of end_date does not require availability) site_ids: optional comma-separated list of site ids to scope the search. Omit to search the whole park. Example: start_date="2026-07-04", end_date="2026-07-07". |
| list_reservationsA | List reservations, optionally filtered by arrival date and status. Use when: "what's arriving this weekend?", "show me pending reservations", "count cancellations last month". Args: start_date: ISO date YYYY-MM-DD — only include reservations whose arrival is on or after this date. end_date: ISO date YYYY-MM-DD — only include reservations whose arrival is on or before this date. status: one of "confirmed", "pending", "cancelled", or other upstream-defined value. Omit for all statuses. limit: page size (server default applies if omitted). offset: zero-based offset for pagination. Example: start_date="2026-07-01", end_date="2026-07-31", status="confirmed", limit=25. |
| get_reservationA | Get a single reservation by id. Use when: "pull up reservation 9384", "what's the balance on booking 1102?", "show me the guest details for reservation 445". |
| list_ratesA | List rate plans at the park, optionally filtered by effective date. Use when: "what rate plans are active in July?", "show me all winter rates", "is the weekend plan still configured?". Args: start_date: ISO date YYYY-MM-DD — only include rate plans effective on or after this date. end_date: ISO date YYYY-MM-DD — only include rate plans effective on or before this date. |
| get_park_infoA | Get metadata about the configured park (name, timezone, contact info). Use when: "which park am I configured for?", "what timezone are reservations in?", "show me the address on file". |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct resource and action: park info, individual reservation, individual site, health check, rate plans, list reservations, list sites, and availability search. No overlap in functionality.
All tool names follow a consistent verb_noun pattern (e.g., get_park_info, list_reservations, search_availability) using lowercase with underscores. No mixed conventions or vague verbs.
8 tools is well-scoped for a campsite management server. It covers essential operations without being overly numerous or sparse.
The tool set covers core read operations and availability search. Missing write operations (e.g., create reservation) but this is likely intentional for a query-focused server.