Summary
Wraps the Recreation Information Database (RIDB) API v1, giving Claude access to federal recreation data managed by Recreation.gov. This is the authoritative source for info on campgrounds, permits, tours, and facilities across thousands of federal recreation sites. Hosted by Pipeworx, which runs it as a managed gateway service alongside 764+ other data sources. You can connect directly to this single server or tap into the full Pipeworx gateway. Supports their ask_pipeworx pattern where you ask questions in plain English instead of calling tools directly. Useful if you're building camping trip planners, availability checkers, or anything that needs real data on national parks, forests, and federal recreation areas.
Fastest browser for AI agents to run web automation tasks, always free.
Download Free life-time →
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
belt cli automatically finds the best tools and skills for your agent. image, video, music, tts...
one prompt install →
Connect your Claude agent to live crypto prices and trading routes via 1inch
Get the MCP →
mcp-recreation-gov
Recreation.gov MCP — wraps the Recreation Information Database (RIDB) API v1
Part of Pipeworx — an MCP gateway connecting AI agents to 1481+ live data sources.
Tools
| Tool | Description |
|---|---|
search_facilities | Search US federal recreation facilities — campgrounds, day-use areas, visitor centers, trailheads — on Recreation.gov. Filter by name/keyword, state, activity (e.g. "camping", "hiking"), or geographic radius. Returns facility IDs, names, types, phone/email, and coordinates. Example: search_facilities({ query: "Yosemite", state: "CA", activity: "camping" }) |
get_facility | Get full details for a single Recreation.gov facility (e.g. a campground) by its FacilityID. Returns description, directions, ADA access, phone/email, keywords, and coordinates. Example: get_facility({ facility_id: "232447" }) |
search_recareas | Search US federal recreation areas — the parent regions (national parks, national forests, BLM/USACE lands) that contain campgrounds and facilities — on Recreation.gov. Filter by name/keyword or state. Returns RecArea IDs, names, descriptions, phone, and coordinates. Example: search_recareas({ query: "Grand Canyon", state: "AZ" }) |
list_campsites | List the individual campsites within a Recreation.gov facility (campground) by FacilityID. Returns campsite IDs, names, type (e.g. "TENT ONLY", "RV"), loop, reservability, and type of use. Example: list_campsites({ facility_id: "232447" }) |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"recreation_gov": {
"url": "https://gateway.pipeworx.io/recreation_gov/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/recreation_gov/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1481+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Recreation Gov data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/recreation_gov_search_facilities \
-H 'Content-Type: application/json' \
-d '{"query":"Yosemite","state":"CA","activity":"camping"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/recreation_gov_search_facilities. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Featured
Fastest browser for AI agents to run web automation tasks, always free.
Download Free life-time →Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →belt cli automatically finds the best tools and skills for your agent. image, video, music, tts...
one prompt install →Connect your Claude agent to live crypto prices and trading routes via 1inch
Get the MCP →