# OpenDataMCP/OpenDataMCP [Health: Active]

**Category:** 👤 Customer Data Platforms  
**Repository:** https://github.com/OpenDataMCP/OpenDataMCP  
**GitHub Stars:** 156  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/opendatamcp-opendatamcp

## Description
Connect any Open Data to any LLM with Model Context Protocol.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "opendatamcp": {
    "command": "uvx",
    "args": ["odmcp"]
  }
}
```

## Documentation

## What OpenDataMCP/OpenDataMCP MCP server does

OpenDataMCP/OpenDataMCP MCP server provides a collection and contribution framework for connecting public datasets to LLM applications through MCP. Each data source is represented by a provider module, allowing the provider to define the interface used by an MCP client.

The repository includes a reference provider for Switzerland’s SBB open-data service. Dataset availability is still developing, and the project is actively seeking additional providers.

## How it works

The project uses Python provider modules under `src/odmcp/providers/`. A provider can implement MCP Tools for active queries, filtering, computation, or transformations. It can instead expose MCP Resources when the source is static, small enough to load into memory, file-based, or intended as reference material.

Provider inputs and outputs are expected to use Pydantic models. The provider template also calls for descriptions, documentation strings, and error handling. This structure gives each dataset an MCP-facing interface while keeping provider-specific behavior in its own module.

OpenDataMCP/OpenDataMCP MCP server currently uses the standard local setup flow described in the README. Support for alternative transports such as SSE and hosted remote servers is listed as future work, not as an available feature in the documented setup.

## Setup and configuration

Install `uv` before using the CLI. On macOS, the documented command is `brew install uv`; Windows instructions use the PowerShell installer. The README specifically documents Claude Desktop as the client and recommends installing its desktop application first.

The package can be run with `uvx odmcp`. The available commands include:

- `uvx odmcp` to display the command list
- `uvx odmcp list` to show providers
- `uvx odmcp info $PROVIDER_NAME` to inspect a provider
- `uvx odmcp setup $PROVIDER_NAME` to configure its MCP server in Claude Desktop
- `uvx odmcp remove $PROVIDER_NAME` to remove that configuration

For example, `uvx odmcp setup ch_sbb` configures the SBB provider. Claude must then be restarted before the provider becomes available.

## Tools and capabilities

The available MCP interface depends on the selected provider; the material does not define one universal set of tool names. The project supports provider-defined Tools and Resources, with schemas and behavior implemented in each module. The CLI supplies provider discovery and local client configuration rather than acting as a general-purpose data query interface itself.

## Limitations and notes

The documented access path starts with Claude Desktop, while support for additional LLM applications is part of the roadmap. Authentication, rate limiting, additional MCP protocol features, SSE transport, and hosted servers are also listed as planned work. Contributions require adding a provider module, tests, validation, and adherence to the repository’s templates and coding practices.

_Full upstream README: https://allmcps.com/mcp/opendatamcp-opendatamcp/readme_