Data Rennes

What the Data Rennes MCP server does

The Data Rennes MCP server gives an MCP-compatible agent access to Rennes Métropole’s public datasets on data.rennesmetropole.fr. Its main workflow is discovery first, inspection second, and querying third. An agent can search for relevant datasets, examine a selected dataset’s fields and metadata, then request records using the available column names.

The service is suited to questions involving local mobility, urban services, environmental information, and geographic data. Search results include dataset identifiers, titles, themes, and record counts, which helps an agent choose a dataset before attempting a query.

How it works

The hosted endpoint is provided through the Pipeworx gateway at https://gateway.pipeworx.io/data-rennes/mcp. A client connects over MCP and can call the pack’s three documented tools: search_datasets, dataset_info, and query.

The recommended sequence is to call search_datasets with a keyword, pass a returned identifier to dataset_info, and use the schema from that response to construct a query call. Queries use ODSQL and can filter records with where, aggregate or select fields with group_by and select, order results with order_by, and paginate through results with limit and offset.

The gateway endpoint also exposes shared Pipeworx meta-tools in addition to the pack-specific tools. These include routing and discovery functions such as ask_pipeworx, discover_tools, and search_within. The local package exposes only the Data Rennes tools and does not add those gateway tools.

Setup and configuration

For a hosted connection, add the following MCP server URL to a compatible client:

{
  "mcpServers": {
    "data-rennes": {
      "url": "https://gateway.pipeworx.io/data-rennes/mcp"
    }
  }
}

The Data Rennes MCP server can also run locally over stdio with the published npm package:

{
  "mcpServers": {
    "data-rennes": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-data-rennes"]
    }
  }
}

Run npx -y @pipeworx/mcp-data-rennes directly to verify that the local process starts. The standalone mode does not require a Pipeworx account or a gateway round trip. No account is needed for the first gateway calls.

Tools and capabilities

• search_datasets: Find Rennes Métropole datasets by keyword and return identifiers, titles, themes, and record counts.
• dataset_info: Inspect a dataset’s fields, schema, themes, and record count.
• query: Retrieve or summarize records with ODSQL filters, grouping, field selection, ordering, limits, and offsets.

Limitations and notes

The hosted pack endpoint lists shared Pipeworx tools alongside its three documented tools, so its tool list is larger than the local package’s list. Its initialize response provides the authoritative scope for a particular connection. The local stdio mode is limited to this pack’s tools and does not provide ask_pipeworx routing.

Queries depend on the dataset’s actual schema. Call dataset_info before query when the required column names are unknown. The available content is limited to datasets published by Rennes Métropole Open Data and the query features supported by the OpenDataSoft interface.