
Nyc Restroom Mcp
io.github.DanielOrtiz0220Published by GitHub account DanielOrtiz0220v0.1.1Updated Oct 24, 2026
Find NYC public restrooms and their latest Parks inspection status, from NYC Open Data
Overview
Lets an assistant find NYC public restrooms near a location and check their latest NYC Parks inspection status.
- What you can do
- Adds two read-only tools backed by NYC Open Data. find_restrooms lists open public restrooms near a location, closest first, with hours, accessibility and changing-station details. get_restroom_status looks up a single restroom by name or coordinates and returns its most recent NYC Parks inspection rating where one exists. If no location is given, it can detect one automatically.
- When to use it
- Useful when you want an assistant to answer practical questions about public bathrooms in New York City, such as finding an open or wheelchair-accessible restroom nearby, or checking how a Parks-run restroom scored in its latest inspection.
- Requirements
- Local process run via npx, so Node.js 20 or newer is needed. No account or authentication is required. Optional environment variables: SOCRATA_APP_TOKEN for higher NYC Open Data rate limits, CORELOCATION_CMD for precise on-device location on macOS, and LOG_LEVEL. Network access is required to reach NYC Open Data.
Installation
In SourceWeft
- Open Nyc Restroom Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
nyc-restroom-mcp
Ask Claude "where's the nearest public bathroom?" and get a real answer.
This is an MCP server, a small plugin that gives an AI assistant (like Claude Desktop or Claude Code) new abilities. This one lets it search New York City's official public restroom data, live from NYC Open Data. Once installed, you can ask things like:
- "Find a public restroom near Union Square that's open right now."
- "Which restrooms near me are wheelchair accessible?"
- "Is the bathroom at Jaime Campiz Playground actually clean?" (it looks up the latest NYC Parks inspection report)
It adds two tools:
If you don't give it a location, it can detect yours automatically (details below). Everything is read-only: it only ever fetches public city data.
Install
You need Node.js 20 or newer. No download or setup beyond the snippet for your app.
Claude Code (one command):
Claude Desktop: go to Settings -> Developer -> Edit Config and add this to
claude_desktop_config.json:
Any other MCP client works the same way: have it launch
npx -y nyc-restroom-mcp as a local (stdio) server.
Good to know
- Automatic location. If you ask for nearby restrooms without saying
where you are, the server tries to figure it out: first from your device
(macOS only, if you
brew install corelocationcliand grant it Location Services access), otherwise a rough guess from your IP address. If neither works, or you're outside NYC, it simply asks for explicit coordinates instead of guessing wrong. - Privacy. Location detection only happens when you omit coordinates, and your location is never written to logs. Pass explicit coordinates and no location lookup happens at all.
- Live data. Every answer comes straight from NYC Open Data (with a short-lived in-memory cache), so results are as current as the city's own records. Inspection reports only exist for restrooms run by NYC Parks; library and other restrooms will honestly say no inspection data exists.
- More detail. The docs/ directory covers the full tool reference, location detection, data sources, configuration, and security model. The reasoning behind every design decision lives in DECISIONS.md.
Optional settings
Set these as environment variables if you need them (most people don't):
A few more exist for testing and advanced setups; see docs/configuration.md.
Contributing
Issues and pull requests are welcome at DanielOrtiz0220/nyc-restroom-mcp.
Development uses Bun (1.1+):
To run your local copy inside an MCP client instead of the published package:
Useful extras: bun run test:live runs one smoke test against the real NYC
Open Data API (needs network), and bun test --coverage reports coverage
(85%+ lines required on src/lib/). Before opening a PR, please make sure
bun test, bun run typecheck, and bun run lint all pass. The full
development guide (test architecture, project structure, invariants to
preserve) is in docs/development.md, and
DECISIONS.md explains why things work the way they do.
License
Source: README.md at commit 60388c6
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts