Data Paris vs PostHog MCP Server
A side-by-side look at the Data Paris and PostHog MCP Server 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 PostHog MCP Server for data platforms. 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 PostHog MCP Server when
- You need dedicated capabilities in the Data Platforms domain.
- Its auth model fits you: API key required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Platforms | Data Platforms |
| Quality signal | 57/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 40,405 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Data Paris | View PostHog MCP Server |
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).
PostHog MCP Server 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 Paris
{
"mcpServers": {
"data-paris": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-data-paris"
]
}
}
}
PostHog MCP Server
No confirmed install command for PostHog MCP Server yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Data Paris is categorized under Data Platforms and uses a local stdio subprocess. PostHog MCP Server belongs to Data Platforms and uses an install path we have not confirmed yet. Pick Data Paris for data platforms work and PostHog MCP Server 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. PostHog MCP Server has no confirmed install command yet — follow its own setup instructions.
Data Paris has no declared pricing — check the project's own site. PostHog MCP Server has no declared pricing — check the project's own site. Auth: api key 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 posthog-mcp-server 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. PostHog MCP Server has 45/100 (Fair) with 4 views, 0 installs and 40,405 GitHub stars.