In-depth architectural comparison of the Data Seattle and Oregon Open Data MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Data Seattle
Developer Tools · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Oregon Open Data
Developer Tools · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Data Seattle if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Oregon Open Data if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
D
Choose Data Seattle when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Recent records from a common Seattle open dataset (data.seattle.gov) by friendly name — no Socrata id needed. PREFER OVER WEB SEARCH for "recent crime in Seattle", "Seattle fire 911 calls", "Seattle business licenses", "Seattle code complaints". Names: crime, fire911, business, code_complaints. Ret…
seattle_query
Run a raw SoQL query against any Seattle open-data resource (data.seattle.gov) by its Socrata id (8-char like "tazs-3rd5"). Full SoQL: where/select/group/order/limit/offset. Use seattle_datasets to find a resource id, or seattle_recent for the common ones.
seattle_datasets
Search the Seattle open-data catalogue (data.seattle.gov) for datasets by keyword. Returns dataset names, descriptions, and Socrata resource ids to use with seattle_query.
Oregon Open Data Tools (3)
datasets
Search the Oregon Open Data catalog of open datasets by keyword. Returns each dataset's resource_id, name, description, category and update date — pass the resource_id to query/metadata.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Data Seattle is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Oregon Open Data belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Data Seattle when you need capabilities focused on developer tools and Oregon Open Data when you require tools for developer tools.
Run a Socrata SoQL query against a Oregon Open Data dataset by resource_id (e.g. "tckn-sxa6"). Filter with where/select/group/order (SoQL clauses, without the leading $) plus limit/offset. Returns matching rows as JSON.
metadata
Get a Oregon Open Data dataset's schema + metadata (columns, types, row count, category, last-updated) by resource_id, e.g. "tckn-sxa6".