Data Paris vs Filesystem
A side-by-side look at the Data Paris and Filesystem MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Data Paris for data platforms work as a local process; choose Filesystem for file systems as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Data Paris when
- You need dedicated capabilities in the Data Platforms domain.
- You prefer a local stdio subprocess transport.
- You want tools like
search_datasets, dataset_info, query.
Choose Filesystem when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
path, head, tail.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Platforms | File Systems |
| Quality signal | 57/100 · Good | 85/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 91,546 |
| Directory activity | 1 views 0 installs 0 upvotes | 11 views 0 installs 0 upvotes |
| Tools | 3 | 17 |
| Full listing | View Data Paris | View Filesystem |
Tools & capabilities
Data Paris tools 3
search_datasetsSearch Paris Open Data for datasets by keyword (city services, mobility, trees, events, urban planning & environment). Returns dataset_ids (pass to query/dataset_info), titles, themes and record counts.dataset_infoGet metadata for one Paris Open Data dataset (fields/schema, themes, record count) — call before query to learn the column names.queryQuery records from a Paris Open Data dataset with ODSQL. Filter (where), aggregate (group_by/select), sort (order_by), paginate (limit/offset).
Filesystem tools 17
pathheadtailpathscontenteditsoldTextnewTextdryRunsortBysourcedestination- +5 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Data Paris
{
"mcpServers": {
"data-paris": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-data-paris"
]
}
}
}
Filesystem
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem"
]
}
}
}
Frequently asked questions
Data Paris is categorized under Data Platforms and uses a local stdio subprocess. Filesystem belongs to File Systems and uses a local stdio subprocess. Pick Data Paris for data platforms work and Filesystem for file systems.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Data Paris has no declared pricing — check the project's own site. Filesystem is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add data-paris and filesystem as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Data Paris has a quality signal of 57/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Filesystem has 85/100 (Excellent) with 11 views, 0 installs and 91,546 GitHub stars.