Main
Use the hosted endpoint first to validate behavior; self-host only when you need isolation or customization.
Adopt a tight loop: search datasets, inspect metadata, then fetch resources only when needed to keep tool calls efficient.
Version-control client configs (where appropriate) so teams can reproduce the same MCP wiring across machines.
Source-backed notes
- README describes an MCP server that lets chatbots search/explore/analyze datasets from data.gouv.fr through conversation.
- README states a public instance is available at
https://mcp.data.gouv.fr/mcpwith no access restrictions. - README includes a Claude Code command:
claude mcp add --transport http datagouv https://mcp.data.gouv.fr/mcp.
FAQ
- Do I need an API key?: For the hosted endpoint, README states it’s publicly available without access restrictions.
- Can I self-host?: Yes — README includes Docker Compose instructions for running your own instance.
- Which client should I start with?: Start with Claude Code (command above) or any MCP client you already run.