Data Rennes vs Jitsu
A side-by-side look at the Data Rennes and Jitsu MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Data Rennes for data platforms work as a local process; choose Jitsu for data platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Data Rennes 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 Jitsu when
- You need dedicated capabilities in the Data Platforms domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Platforms | Data Platforms |
| Quality signal | 57/100 · Good | 62/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 5,113 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Data Rennes | View Jitsu |
Tools & capabilities
Data Rennes tools 3
search_datasetsSearch Rennes Métropole Open Data for datasets by keyword (mobility, urban services, environment & geography). Returns dataset_ids (pass to query/dataset_info), titles, themes and record counts.dataset_infoGet metadata for one Rennes Métropole Open Data dataset (fields/schema, themes, record count) — call before query to learn the column names.queryQuery records from a Rennes Métropole Open Data dataset with ODSQL. Filter (where), aggregate (group_by/select), sort (order_by), paginate (limit/offset).
Jitsu tools
No tool names declared yet. Check the project README from 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 Rennes
{
"mcpServers": {
"data-rennes": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-data-rennes"
]
}
}
}
Jitsu
{
"mcpServers": {
"jitsu": {
"url": "https://api.producthunt.com/widgets/embed-image/v1/featured.svg?post_id=297526&theme=neutral"
}
}
}
Frequently asked questions
Data Rennes is categorized under Data Platforms and uses a local stdio subprocess. Jitsu belongs to Data Platforms and uses a remote HTTP/SSE transport. Pick Data Rennes for data platforms work and Jitsu for data platforms.
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 Rennes has no declared pricing — check the project's own site. Jitsu has no declared pricing — check the project's own site. Auth: oauth 2.0. 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-rennes and jitsu as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Data Rennes has a quality signal of 57/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Jitsu has 62/100 (Good) with 1 views, 0 installs and 5,113 GitHub stars.