Data Aixmarseille

What Data Aixmarseille does

Data Aixmarseille exposes Aix-Marseille-Provence Open Data through the Model Context Protocol. The connected portal is data.ampmetropole.fr, with datasets covering areas such as mobility, urban services, and the environment.

The integration is an independent, unofficial connection to the upstream open-data service. It runs through Pipeworx, which provides the hosted MCP endpoint and a local npm bridge. The same gateway also connects to other data sources, but this pack focuses on Aix-Marseille-Provence datasets.

How it works

A typical agent workflow starts by searching for a relevant dataset. The search response includes dataset identifiers, names, themes, and record counts. The agent can then inspect one dataset's metadata to learn its available fields and schema before constructing a query.

Queries use ODSQL and can retrieve records or produce grouped results. Parameters support filtering with where, selecting or aggregating fields with select and group_by, ordering with order_by, and paging through results with limit and offset.

The hosted endpoint is:

https://gateway.pipeworx.io/data-aixmarseille/mcp

A full Pipeworx gateway endpoint is also available. Both routes use the same gateway and can reach the wider catalog through the shared ask_pipeworx capability. Pack endpoints list the pack's own tools together with shared Pipeworx meta-tools; the exact list is returned during MCP initialization.

Setup and configuration

For an MCP client with remote HTTP support, add the hosted endpoint to its MCP server configuration. The package documentation shows compatibility with Claude Desktop, Cursor, and Windsurf.

A local stdio option is available through npm:

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

The bridge forwards requests to the hosted Pipeworx endpoint and requires network access. It does not provide an offline mode. Anonymous use is limited to 50 calls per day. Setting PIPEWORX_API_KEY with a key from Pipeworx raises the allowance to 200 calls per day; requests use the key as a Bearer token and are metered through the gateway.

Set PIPEWORX_META_TOOLS=1 if the local bridge should also list shared gateway tools such as ask_pipeworx. Without it, the bridge lists the Aix-Marseille-Provence pack tools by default. When using an HTTPS proxy, newer Node.js releases can be configured with NODE_USE_ENV_PROXY=1 because Node's built-in fetch does not otherwise read HTTPS_PROXY by default.

Tools and capabilities

• search_datasets finds portal datasets by keyword and returns identifiers, titles, themes, and record counts.
• dataset_info returns metadata, fields, schema details, themes, and record counts for a selected dataset.
• query runs ODSQL queries with filtering, aggregation, selection, ordering, and pagination.
• The Pipeworx gateway can route natural-language requests through ask_pipeworx, including requests that require tools outside this data pack.

The tools can also be called over HTTP without an MCP client. For example, the gateway exposes tool routes under /v1/tools/, including a route for dataset search.

Limitations and notes

The service depends on network access to the Pipeworx gateway and the upstream data source. Anonymous calls have a daily limit, while authenticated calls are subject to Pipeworx metering and billing. Pack connections necessarily expose shared gateway meta-tools in addition to the pack-specific tools, although the local npm bridge can hide them from its default tool listing. This integration is not affiliated with or endorsed by Aix-Marseille-Provence or the upstream portal.