Nyc311 Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.6Updated Nov 3, 2026

MCP server for NYC 311 public service request search and aggregate civic data.

VerifiedSTDIODesktop onlyData & Analytics

Overview

Nyc311's local MCP server; no sign-in required; STDIO; 5 tools.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Nyc311 Mcp in the dashboard and add it to a workspace.
  2. 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

nyc311-mcp

Explore public NYC 311 service-request data for civic research, neighborhood-level trend analysis, and city-service questions.

Tools

  • search_requests: search bounded request metadata by complaint type, borough, agency, and dates.
  • count_requests: aggregate request totals by complaint type with the same filters.

The server intentionally excludes street addresses, latitude, longitude, and other precise location fields. NYC 311 records are reports of requests, not verified findings, and may contain reporting delays or duplicates. The public Socrata API requires no key for these read-only queries.

Run

bash
npm installnpm run buildnode dist/index.js

Source: README.md at commit ccbbe5d

Tools

5

search_requests

Search recent public NYC 311 requests using non-location-identifying fields. Addresses and coordinates are intentionally excluded.

ParametersendlimitstartagencyboroughcomplaintType

count_requests

Count NYC 311 requests grouped by complaint type with optional date, borough, and agency filters.

ParametersendlimitstartagencyboroughcomplaintType

request_detail

One NYC 311 request by its unique key.

ParametersuniqueKeyrequired

agency_breakdown

Request counts per agency with optional date filters.

Parametersendlimitstart

daily_trend

Daily request counts for the last N days.

ParametersdaysboroughcomplaintType

Version history

2
  1. v1.0.6LatestOct 29, 2026
  2. v1.0.0Sep 22, 2026

Score

80% 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
  • 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.