Do I need an API key?

No. opendata.paris.fr serves all city datasets anonymously over its Opendatasoft REST API. This MCP defines no credentials and needs nothing configured.

How are the road names stored?

UPPERCASE with a type suffix in parentheses, e.g. "LEGENDRE (RUE)" or "CINQ MARS (AVENUE)". The voie filter is an exact match on the stored label — fetch a page of list_light_fixtures to see the exact forms.

What does the public/private split mean?

voie_categorie separates the network between streets maintained on public land (VOIES PUBLIQUES) and privately owned roads lit by the city (VOIES PRIVEES) — public_private_split returns both totals plus the grand total in one call.

Is this a live sensor feed?

No. The dataset is the city's fixed asset register of each fixture — its code, location, lamp/support family and lighting regime. It is not a dimming, outage or occupancy feed.

Paris Lighting: Street-Light Inventory MCP Connector for Claude

A+

Keyless Paris street-light inventory: the 165,000+ public fixtures — code, road, public/private category, maintenance sector, arrondissement, lamp and support families.

7 tools Official Updated Oct 1, 2026 Official Vinkius Partner

More Details Connect to Claude

Paris's public street-light inventory (eclairage public) — keyless, straight from the Paris open-data platform (opendata.paris.fr).

What you can do

list_light_fixtures / light_fixture_lookup / count_light_fixtures — the ~165,000 fixtures: code (cod_ouvrag, the lookup key), work type, lighting regime, maintenance notes, WGS84 coordinates, the road label as stored (UPPERCASE), the road category (public / private), the maintenance sector and the zero-padded arrondissement label
fixtures_by_road — how many lamps sit on one road, with the first page of them
public_private_split — the three totals: whole network, public roads and private roads
arrondissement_lighting — one arrondissement's fixture count
lighting_overview — the preset facets: top maintenance sectors, top lamp and support families, and the regime / road-category splits

Who is this for

Urban designers, journalists on lighting quality, and anyone locating a fixture by its code or counting the lamps on a street. Road labels are stored UPPERCASE with a type suffix (e.g. "LEGENDRE (RUE)"); arrondissements use the zero-padded label "Arrondissement NN", which the tools map from a plain 1..20 number for you. The dataset is the city's fixed asset register — where each fixture is, what it is and its regime — not a live dimming or outage feed.

parisfrancelightingstreet-lightsluminairesurban-infrastructurekeyless

7 tools expose this connector's capabilities to your AI agent.

arrondissement_lighting

arrondissement is required: the number 1..20, mapped to the stored zero-padded label ("Arrondissement 06" for 6). Count the fixtures in one arrondissement

count_light_fixtures

20, mapped to the stored label), voie (stored UPPERCASE road label), voie_categorie ("VOIES PUBLIQUES" / "VOIES PRIVEES") and secteur (stored sector label) — the same exact-match filters as list_light_fixtures. A fast total count; use it to gauge how many lamps a street or sector has. Count street-light fixtures by road, category, sector or arrondissement

lighting_overview

No parameters. Overview of the street-light inventory: top sectors, lamps, supports, regimes

fixtures_by_road

voie is required — the stored UPPERCASE road label (voie_libelle), e.g. "LEGENDRE (RUE)". Optionally restrict to one road category (voie_categorie: "VOIES PUBLIQUES" / "VOIES PRIVEES"). Count and list the fixtures on one road

light_fixture_lookup

g. "O10721") exactly matches the given value. cod_ouvrag is required; 0 or 1 row comes back with the work type, lighting regime, maintenance notes, road, sector and coordinates. Look up a street-light fixture by its code

list_light_fixtures

Each row has the fixture code (cod_ouvrag, e.g. "O10721" — the lookup key), the work type (lib_ouvrag, e.g. "Candélabre"), the lighting regime (lib_regime, e.g. "HORAIRE EP"), maintenance notes (observatio), the WGS84 coordinates as text (x_wgs84 / y_wgs84), the road label as stored (voie_libelle, UPPERCASE, e.g. "LEGENDRE (RUE)"), the road category (voie_categorie: "VOIES PUBLIQUES" or "VOIES PRIVEES"), the maintenance sector (secteur_libelle, e.g. "15_NECKER") and the arrondissement label (zero-padded, "Arrondissement 06".."Arrondissement 20"). All columns are exact-match text filters; pass arrondissement as the number 1..20 and it is mapped to its stored label. Page with limit/offset (100 rows max per call). List the public street-light fixtures of Paris

public_private_split

Shows how much of the city lighting stock lives on publicly owned streets. No parameters. Split the fixture inventory between public and private roads

Connect to Claude

Subscribe on Vinkius, then add this connector to Claude.ai or Claude Code.

① Claude.ai (web app)

Go to Settings → Connectors → Add custom connector
Paste the MCP endpoint URL below

https://edge.vinkius.com/vk_preview_rZXYBE4zv6L51gQ78bQCWvMQbXKKnwDmXNIkQGiZ/mcp

② Claude Code (terminal)

claude mcp add --transport http paris-lighting-street-light-inventory https://edge.vinkius.com/vk_preview_rZXYBE4zv6L51gQ78bQCWvMQbXKKnwDmXNIkQGiZ/mcp

③ Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "paris-lighting-street-light-inventory": {
      "url": "https://edge.vinkius.com/vk_preview_rZXYBE4zv6L51gQ78bQCWvMQbXKKnwDmXNIkQGiZ/mcp"
    }
  }
}

Get full access on Vinkius

The preview token above works for testing. Powered by Vinkius.