Beta MCPs
BetaNYC builds free, open-source MCP servers that let AI assistants such as Claude work with NYC and New York State civic data. Before a big change is released, we ask staff and community members to try it. This page lists what is in testing right now.
What a beta is
- It is unreleased. A beta runs straight from the repository’s
mainbranch on GitHub, ahead of the next npm release. Anyone using the released version from npm keeps the released version. Nothing changes for them. - It may change, or break, without notice. Tools can be renamed, answers can change shape, and a fix can land between one day and the next.
- Its answers still need checking. Compare anything important with the source the answer links to.
- You can switch back at any time. Each beta page shows how.
In testing now
Nothing right now.
Released
| MCP | Released | Notes |
|---|---|---|
@betanyc/nyc-311-mcp |
1.2.0, November 9, 2026 | The beta’s 21 tools. Install guide · what the beta was |
How to give feedback
Open a beta feedback issue on the MCP’s GitHub repository. Tell us which tool, what you asked, what you got, and what you expected. GitHub issues are public, so leave out names, phone numbers, email addresses, home addresses, and anything else about a real person.
Adding a beta to this page (for maintainers)
- Merge the work to
mainand confirm it installs withnpx -y github:BetaNYC/<repo>#mainand answers an MCPtools/list. Testers install from#main. Do not make a separate, long-lived beta branch: nyc-311-mcp’sbetabranch fell behindmainand sent testers an old build. - Add a row to the table above and a page next to this one,
docs/beta/<repo>.md, following the nyc-311-mcp page: what is new, install, what to test, safety notes if any, feedback, switching back. - Add a
beta-feedback.ymlissue form to that repository’s.github/ISSUE_TEMPLATE/. - When the beta is released, move its row to a “Released” note and point the page at the npm package.