mcp-data-issy
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-data-issysearch for datasets about public transport"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-data-issy
Issy-les-Moulineaux Open Data (data.issy.com) — OpenDataSoft MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tools
Tool | Description |
| Search Issy-les-Moulineaux Open Data for datasets by keyword (city services, mobility, environment & smart-city data). Returns dataset_ids (pass to query/dataset_info), titles, themes and record counts. |
| Get metadata for one Issy-les-Moulineaux Open Data dataset (fields/schema, themes, record count) — call before query to learn the column names. |
| Query records from a Issy-les-Moulineaux Open Data dataset with ODSQL. Filter (where), aggregate (group_by/select), sort (order_by), paginate (limit/offset). |
Related MCP server: data-bs-mcp
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"data-issy": {
"url": "https://gateway.pipeworx.io/data-issy/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/data-issy/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Data Issy data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Île-de-France Open Data (data.iledefrance.fr) — OpenDataSoft MCP.
Paris Open Data (opendata.paris.fr) — OpenDataSoft MCP.
MCP server for French (BOAMP) + EU (TED) public procurement data via TenderAPI.
Tours Métropole Open Data (data.tours-metropole.fr) — OpenDataSoft MCP.
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server for exploring French public open data via APIs like data.gouv.fr, geo.api.gouv.fr, INSEE Sirene, and Radio France.11MIT
- FlicenseAqualityCmaintenanceMCP server for querying Huwise/Opendatasoft data portals. Enables dataset search, metadata retrieval, record filtering with ODSQL, and data export.53-
- FlicenseNot gradedqualityDmaintenanceMCP server to navigate and consume public data from Benin's OpenData portal.-
- FlicenseNot gradedqualityDmaintenanceMCP server to query French Open Data from data.gouv.fr-