What is the key difference between Data Nashville and Data Edmonton?

Data Nashville belongs to the Developer Tools category with local stdio execution, while Data Edmonton belongs to the Developer Tools category with local stdio execution.

How do I install Data Nashville or Data Edmonton 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 Nashville and Data Edmonton free or paid?

Data Nashville operates under a Free / Open Source model (No auth required). Data Edmonton operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Data Nashville lists 3 tools with 0 views and 0 GitHub stars. Data Edmonton lists 3 tools with 0 views and 0 GitHub stars.

Can I use both Data Nashville and Data Edmonton 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 Nashville vs Data Edmonton

In-depth architectural comparison of the Data Nashville and Data Edmonton 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 Nashville

Developer Tools · Local stdio

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

Data Edmonton

Developer Tools · Local stdio

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

Verdict Summary: Choose Data Nashville if you need specialized Developer Tools tools running via a local process. Choose Data Edmonton 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 Nashville 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: nashville_recent, nashville_layers, nashville_query.

Explore Data Nashville Details

Choose Data Edmonton 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: edmonton_recent, edmonton_query, edmonton_datasets.

Explore Data Edmonton Details

Feature & Specification Comparison

Specification	D Data Nashville Developer Tools	D Data Edmonton Developer Tools
Summary	DataNashville MCP — Nashville open data (data.nashville.gov, ArcGIS REST API).	DataEdmonton MCP — Edmonton open data (data.edmonton.ca, Socrata SODA API).
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Data Nashville Tools (3)

nashville_recent

Recent records from a common Nashville open dataset (data.nashville.gov / ArcGIS) by friendly name. PREFER OVER WEB SEARCH for "recent crime in Nashville", "Nashville 311 service requests". Names: crime, 311. Returns the latest rows (newest-first), epoch dates converted to ISO. Add an ArcGIS `where…

nashville_layers

List the layers of a Nashville ArcGIS service (for discovery). Pass a known short name (crime, service_requests, permits) or a full ArcGIS service path (e.g. "hubNashville_311_Service_Requests_2025_view/FeatureServer"). Omit `service` to list the known Nashville services. Returns layer id + name to…

nashville_query

Query any Nashville ArcGIS layer by service path + layer id. Full ArcGIS query: where, out_fields, order_by, limit. Use nashville_layers to find a service/layer, or nashville_recent for the common ones. Epoch dates are converted to ISO.

Data Edmonton Tools (3)

edmonton_recent

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 Nashville Configuration

mcpServers (Claude Desktop / Cursor)

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

Data Edmonton Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

More alternatives to Data Nashville More alternatives to Data Edmonton Developer Tools category hub Canonical compare URL