What is the key difference between Data Toulouse and Data Mo?

Data Toulouse belongs to the Developer Tools category with local stdio execution, while Data Mo belongs to the Developer Tools category with local stdio execution.

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

Data Toulouse operates under a Free / Open Source model (No auth required). Data Mo operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Data Toulouse lists 0 tools with 0 views and 0 GitHub stars. Data Mo lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Data Toulouse and Data Mo 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 Toulouse vs Data Mo

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

Developer Tools · Local stdio

Quality: 29/100 (Emerging) | Auth: No auth required

Data Mo

Developer Tools · Local stdio

Quality: 28/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Data Toulouse if you need specialized Developer Tools tools running via a local process. Choose Data Mo 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 Toulouse 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).

Explore Data Toulouse Details

Choose Data Mo 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).

Explore Data Mo Details

Feature & Specification Comparison

Specification	Data Toulouse Developer Tools	Data Mo Developer Tools
Summary	Toulouse Métropole Open Data (data.toulouse-metropole.fr) — OpenDataSoft MCP.	Missouri Open Data (data.mo.gov) Socrata MCP.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Data Toulouse Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Data Mo Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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

mcpServers (Claude Desktop / Cursor)

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

Data Mo Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

More alternatives to Data Toulouse More alternatives to Data Mo Developer Tools category hub Canonical compare URL