Seattle 911 Incidents (example) — socrata mcp server MCP Resource

Seattle 911 Incidents (example) is one of 2 resources on the socrata mcp server MCP server. Connect the server and your client can attach it as context.

by client

How to attach Seattle 911 Incidents (example) from your client

• Claude Code socrata mcp server Resource/Seattle 911 Incidents (example) run in your project directory
• Claude Desktop socrata mcp server Resource/Seattle 911 Incidents (example) ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor socrata mcp server Resource/Seattle 911 Incidents (example) ~/.cursor/mcp.json
• VS Code socrata mcp server Resource/Seattle 911 Incidents (example) .vscode/mcp.json
• Zed socrata mcp server Resource/Seattle 911 Incidents (example) ~/.config/zed/settings.json
• Windsurf socrata mcp server Resource/Seattle 911 Incidents (example) ~/.codeium/windsurf/mcp_config.json
• Cline socrata mcp server Resource/Seattle 911 Incidents (example) ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI socrata mcp server Resource/Seattle 911 Incidents (example) ~/.gemini/settings.json
• Grok socrata mcp server Resource/Seattle 911 Incidents (example) .mcp.json (in your project root)
• ChatGPT socrata mcp server Resource/Seattle 911 Incidents (example) Settings → Connectors → Advanced → Developer mode
• Claude.ai socrata mcp server Resource/Seattle 911 Incidents (example) Settings → Connectors → Add custom connector
• LangChain socrata mcp server Resource/Seattle 911 Incidents (example) pip install langchain-mcp-adapters

Other resources on this server

• socrata-portals

socrata mcp server also offers 1 prompt — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.