Luxembourg MCP: public data, ready for agents

• By amirdaraee • 2 min read
Featured image for Luxembourg MCP: public data, ready for agents

Luxembourg MCP: public data, ready for agents

Luxembourg publishes a lot of public data: laws, statistics, live parking, water levels, air quality, parliamentary questions. The problem is that it lives in 18 different systems, each with its own API shape, format, and quirks. If you want an AI agent to answer “what weather warnings are active right now?”, someone has to do the integration work first.

So I did it once, for everyone. Luxembourg MCP is a Model Context Protocol server that turns those fragmented sources into 27 consistent tools any MCP client can call. There’s a hosted endpoint at luxembourg-mcp.com, so you don’t even need to install anything.

Credit where it’s due

The idea comes from Allemannsdata by Thomas Heggelund, which does this for Norwegian public data. The name references allemannsretten, Norway’s right to roam: public information should be as easy to reach as public land. Luxembourg MCP applies that idea to the Grand Duchy as an independent implementation.

What’s inside

  • 27 tools over 18 public systems. Legislation, STATEC statistics, geocoding, transit stops, election results, housing prices, EV charging.
  • No API keys, no accounts. Every source is keyless. Point a client at the endpoint and start asking questions.
  • No scraping. Everything comes from official APIs and open datasets.
  • Traceable answers. Every result carries the upstream source URL, so you can always check the authoritative record.
  • Live data included. City parking, P+R occupancy, motorway traffic, water levels, weather at Findel.

What an agent can do with it

Once connected, an agent can answer things like:

  • How many spaces are free at the Belval P+R right now?
  • Find legislation concerning pensions.
  • What are advertised house prices in Esch-sur-Alzette?
  • Which bus or tram stops match Hamilius?
  • What’s the current air quality in Luxembourg City?

Try it

Point any MCP client at the hosted endpoint:

{
  "mcpServers": {
    "luxembourg": {
      "url": "https://mcp.luxembourg-mcp.com/mcp"
    }
  }
}

Or run it locally with uvx luxembourg-mcp. The README covers Docker, security notes, and the full tool catalogue.

If a data source you need is missing, open an issue. The list of candidates is long and I’d rather build what people actually use.

Related posts