# NYC 311 Service Requests AI Agent Connect > NYC 311 Service Requests MCP gives your AI client direct access to over 22 million service requests and call center inquiries from NYC Open Data. You can filter by borough, complaint type, or date to find specific pothole reports, noise complaints, or streetlight issues. It also includes a historic dataset covering 2010 to 2019 and detailed call center inquiry logs. ## Overview - **Category:** government-public-data - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_5O2OKLZxpvCXxshEFfzf52E2LQ1W1X7ixWlPQxMl/ai-agent-connect - **Tags:** new-york, nyc, 311, service-requests, complaints, government-public-data ## Description You can now give your AI agent a direct line to New York City's non-emergency service data. This MCP connects your client to the massive NYC Open Data repository, covering everything from rodent complaints and water leaks to code enforcement and street conditions. Whether you are looking for recent trends or deep historical context, the data is right there. You can use it to track how specific agencies like the DOT or NYPD are handling neighborhood issues. If you need to know why a certain area is seeing a spike in noise complaints, you can filter by borough or date to see the exact volume. It even handles the call center side of things, letting you see how information requests were resolved. Instead of manually digging through web portals, you just ask your agent to find the data for you. ## Tools ### count_311_requests This tool counts 311 service requests based on your specific filters. Use it to get a total volume of complaints before you pull individual records. ### get_311_request This tool retrieves a single service request using its 10-digit unique key. It automatically checks the current dataset before falling back to historic records from 2010 to 2019. ### search_311_inquiries This tool searches 311 call center inquiries dating back to 2014. It returns descriptions of information requests and how the call center resolved them. ### search_311_requests This tool searches the main 311 service request database using filters like complaint type, agency, borough, or date. It covers all requests from 2020 to the present. ### top_311_complaints This tool identifies the most frequent complaint types within a specific timeframe. You can adjust the number of days to look back to see recent trends. ## Prompt Examples **Prompt:** ``` What are the top 311 complaints in the last two weeks? ``` **Response:** ``` The most frequent complaints over the last 14 days are: 1. Noise, 2. Street Condition, 3. Illegal Parking. ``` **Prompt:** ``` How many open pothole complaints in Queens? ``` **Response:** ``` There are currently 142 open pothole complaints in Queens. ``` **Prompt:** ``` Tell me about 311 request 70518024 ``` **Response:** ``` Request 70518024 is a Street Condition complaint regarding a pothole in Manhattan. The status is Closed and the agency involved was the DOT. ``` ## Capabilities ### Trend Analysis Your agent uses top complaint data to identify emerging city-wide issues. ### Specific Record Retrieval Your agent pulls full details for a single complaint using its unique ID. ### Volume Calculation Your agent calculates the exact number of matching complaints for any filtered criteria. ### Historical Lookups Your agent accesses records from the 2010 to 2019 period when searching for specific keys. ### Call Center Auditing Your agent examines how call center inquiries and information requests were handled. ## Use Cases ### Neighborhood Issue Tracking Check how many noise complaints have been filed in Brooklyn over the last month. ### Agency Performance Review Compare the volume of requests handled by the DOT versus the DEP. ### Journalistic Fact Checking Verify if a reported increase in rodent sightings is backed by 311 data. ### Civic Planning Identify high-traffic complaint areas to inform local infrastructure discussions. ## Benefits - Accesses over 22 million records without needing an API key. - Automates the switch between current and historic datasets. - Provides direct access to agency-specific complaint codes. - Eliminates manual filtering through the NYC Open Data web interface. ## How It Works Connecting to this MCP gives your AI client immediate access to NYC's live service datasets. 1. Connect your MCP-compatible client to Vinkius. 2. Select the NYC 311 Service Requests MCP from the catalog. 3. Ask your agent a question about NYC service requests or complaints. 4. The agent uses the appropriate tool to query the NYC Open Data sets. 5. The agent receives the raw data and presents the answer to you. ## Frequently Asked Questions **Do I need an API key to use this MCP?** No, this MCP works without an API key. Vinkius handles the connection to NYC Open Data for you. **How far back does the data go?** The current dataset covers 2020 to the present, and there is a historic dataset available for 2010 through 2019. **Can I search for specific boroughs?** Yes, you can filter searches by borough using uppercase names like MANHATTAN or BROOKLYN. **What kind of complaints can I find?** You can find data on potholes, noise, streetlights, water leaks, rodent complaints, and more. **Which AI clients can use this?** Any MCP-compatible client like Claude, Cursor, Windsurf, or VS Code can use this MCP. **Do I need an API key?** No. NYC Open Data serves all public datasets anonymously over its SODA API (data.cityofnewyork.us). This MCP defines no credentials and needs nothing configured. **Borough values differ across datasets — how do I know the format?** Formats are dataset-specific: 311 and shootings use UPPERCASE ("QUEENS"), food and sanitation use Title Case ("Queens"), DOT potholes use single-letter codes. Tool descriptions state the expected values, and the errors from a mismatched value are reported verbatim by the platform. **How far back does the 311 data go?** The main dataset covers 2020 onward (22M+ rows). Requests from 2010-2019 live in the companion historic dataset; get_311_request checks both, so a lookup by unique key works for either era.