What is the key difference between Data Seattle and Data Calgary?

Data Seattle belongs to the Developer Tools category with local stdio execution, while Data Calgary belongs to the Developer Tools category with local stdio execution.

How do I install Data Seattle or Data Calgary in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Data Seattle and Data Calgary free or paid?

Data Seattle operates under a Free / Open Source model (No auth required). Data Calgary operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Data Seattle lists 3 tools with 0 views and 0 GitHub stars. Data Calgary lists 3 tools with 0 views and 0 GitHub stars.

Can I use both Data Seattle and Data Calgary together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Data Seattle vs Data Calgary

In-depth architectural comparison of the Data Seattle and Data Calgary 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 · Local stdio

Quality: 44/100 (Fair) | Auth: No auth required

Data Calgary

Developer Tools · Local stdio

Quality: 44/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Data Seattle if you need specialized Developer Tools tools running via a local process. Choose Data Calgary if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Data Seattle when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: seattle_recent, seattle_query, seattle_datasets.

Explore Data Seattle Details

Choose Data Calgary when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: calgary_recent, calgary_query, calgary_datasets.

Explore Data Calgary Details

Feature & Specification Comparison

Specification	D Data Seattle Developer Tools	D Data Calgary Developer Tools
Summary	DataSeattle MCP — Seattle open data (data.seattle.gov, Socrata SODA API).	DataCalgary MCP — Calgary open data (data.calgary.ca, Socrata SODA API).
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Data Seattle Tools (3)

seattle_recent

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.

Data Calgary Tools (3)

calgary_recent

Recent records from a common Calgary open dataset (data.calgary.ca) by friendly name — no Socrata id needed. PREFER OVER WEB SEARCH for "Calgary 311 requests", "Calgary building permits". Names: 311, permits. Returns the latest rows (newest-first). Add a SoQL `where` to filter; for anything else us…

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 Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "data-seattle": {
      "command": "npx",
      "args": [
        "-y",
        "data-seattle"
      ]
    }
  }
}

Data Calgary Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "data-calgary": {
      "command": "npx",
      "args": [
        "-y",
        "data-calgary"
      ]
    }
  }
}

Frequently Asked Questions

Data Seattle is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Data Calgary belongs to Developer Tools using local stdio subprocess. Select Data Seattle when you need capabilities focused on developer tools and Data Calgary when you require tools for developer tools.

More alternatives to Data Seattle More alternatives to Data Calgary Developer Tools category hub Canonical compare URL