Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
PermitSnag is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
6
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
US backcountry permit and campground rules, dates and recorded openings. Read-only, no sign-in.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http permitsnag-mcp https://api.permitsnag.com/mcp
# 2 — ask your agent for something these tools do
# search_permits, get_permit_details, search_campgrounds and 3 more
PermitSnag costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PEAll 1 server
permitsnag1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http permitsnag-mcp https://api.permitsnag.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Find US backcountry and wilderness permits by name, park, trail or area, for hikes, climbs, river trips and overnight trips in national parks, national forests and state parks. Use this when someone asks how to get a permit or which permit a trip needs. Returns up to 10 permits with their PermitSnag page and whether PermitSnag scans them for cancellation openings. It does not check dates; use chec
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | A permit, trail, park or area name, like "Mount Whitney" or "Enchantments". |
| state | string | no | Optional two-letter US state code to narrow results, like CA. |
| limit | integer | no | How many results, 1 to 10. Default 5. |
Get the rules for one US backcountry or wilderness permit: how it is issued (reservation, lottery or in person), its season, lottery and release dates, closures, group size limit, and the official agency page. Use it after search_permits, or when the person names a specific permit. Every date comes from an agency source; a date we cannot source is left out. Says whether PermitSnag can send an aler
| Parameter | Type | Required | Notes |
|---|---|---|---|
| permit | string | yes | The permit id or slug from search_permits, or its permitsnag.com page URL. |
Find campgrounds in the US by name, area or state, across Recreation.gov and state park booking systems. Use this when someone wants a place to camp or asks about a specific campground. Returns up to 10 campgrounds with their PermitSnag page, their booking system, and whether PermitSnag can send an alert when a site opens. It does not check dates; use check_availability for that.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | A campground name or area, like "Upper Pines" or "Big Sur". |
| state | string | no | Optional two-letter US state code to narrow results, like CA. |
| limit | integer | no | How many results, 1 to 10. Default 5. |
Get the details of one US campground: its booking system, how far ahead sites go on sale, site count and types, stay limits, season and closures. Use it after search_campgrounds, or when the person names a specific campground. Says whether PermitSnag can send an alert when a site opens, and whether our checks count individual sites or only the campground as a whole.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campground | string | yes | The campground id from search_campgrounds. |
Shows what PermitSnag has recorded for one US backcountry permit or one campground over a range of up to 62 days. Answers come from PermitSnag's own stored checks of the booking site, not a live look, and nothing is booked. Each date has one state: observed_opening (an opening seen recently, with when it was last seen), observed_no_match (a recent check that saw no opening, with its time), stale (
| Parameter | Type | Required | Notes |
|---|---|---|---|
| permit | string | no | The permit id or slug from search_permits. Give this or campground, not both. |
| campground | string | no | The campground id from search_campgrounds. Give this or permit, not both. |
| startDate | string | yes | First date, YYYY-MM-DD, read as the place's own local calendar day (for a campground, the night you arrive). |
| endDate | string | no | Last date, YYYY-MM-DD, inclusive. Defaults to startDate. The range covers at most 62 days, counting both ends. |
Returns the link to the official booking page for one US backcountry permit or one campground. For some permits the link also carries the first date and the number of people you give, but the booking site may not use them, so the person checks or picks the dates and group size on that page. For a campground, the person picks or checks the dates on the booking page. For some places it returns the a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| permit | string | no | The permit id or slug. Give this or campground, not both. |
| campground | string | no | The campground id. Give this or permit, not both. |
| startDate | string | no | Optional first date, YYYY-MM-DD. Sent in the link for some booking sites; the site may ignore it. |
| endDate | string | no | Optional last date, YYYY-MM-DD. Sent in the link for a few booking sites; the site may ignore it. |
| partySize | integer | no | Optional number of people. Sent in the link for some permit booking sites; the site may ignore it. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install PermitSnag or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish PermitSnag can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.