Campertunity MCP Server

Created By
campertunitya year ago
Search campgrounds around the world on campertunity, check availability, and provide booking links
Overview

What is Campertunity MCP Server?

Campertunity MCP Server is a server that implements the Model Context Protocol (MCP) for Campertunity, allowing users to search for campgrounds around the world, check availability, and provide booking links.

How to use Campertunity MCP Server?

To use the server, you need to set up your API key and run the server using the provided command. You can search for campgrounds, check their availability, and book sites through the available tools.

Key features of Campertunity MCP Server?

  • Search for camping places with various filters and criteria.
  • Get detailed information about specific camping places.
  • Check availability of camping sites.
  • Book camping sites directly through the server.

Use cases of Campertunity MCP Server?

  1. Finding suitable campgrounds for family trips.
  2. Checking availability for camping sites during peak seasons.
  3. Booking camping sites for outdoor recreational activities.

FAQ from Campertunity MCP Server?

  • How do I get my API key?

You can obtain your API key from Campertunity's website.

  • Can I filter my campground search?

Yes! You can filter your search by various parameters such as location, amenities, and activities.

  • Is there a limit to the number of results I can get?

Yes, the default limit is 50 results, but you can set it to a maximum of 1000.

Server Config

{
  "mcpServers": {
    "campground-search-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "campertunity-mcp-server@latest"
      ],
      "env": {
        "CAMPERTUNITY_API_KEY": "your_api_key_here"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
campertunity
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 hours ago