Data Reunion vs Cms — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Data Reunion vs Cms
In-depth architectural comparison of the Data Reunion and Cms MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Data Reunion
Developer Tools · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
Cms
Developer Tools · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Data Reunion if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Cms if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
D
Choose Data Reunion when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Search Réunion Open Data for datasets by keyword (regional services, transport, environment & economy). Returns dataset_ids (pass to query/dataset_info), titles, themes and record counts.
dataset_info
Get metadata for one Réunion Open Data dataset (fields/schema, themes, record count) — call before query to learn the column names.
query
Query records from a Réunion Open Data dataset with ODSQL. Filter (where), aggregate (group_by/select), sort (order_by), paginate (limit/offset).
Cms Tools (3)
search_datasets
Find CMS dataset IDs + titles by keyword. CMS publishes Medicare/Medicaid open data (provider data, spending, enrollment, drug pricing, quality measures, hospitals, nursing homes, ACOs, etc.). Searches the CMS DCAT catalog client-side over each dataset title/description/keywords. Returns the datase…
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Data Reunion is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Cms belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Data Reunion when you need capabilities focused on developer tools and Cms when you require tools for developer tools.
Pull rows from a CMS dataset by datasetId (UUID from search_datasets). Returns an array of row objects whose keys are the dataset columns. Supports paging (size/offset), full-text keyword search across the dataset, and exact-match column filters via filters: {COLUMN: VALUE} (column names match the…
dataset_info
Metadata for a CMS dataset by datasetId: title, description, total row count, last-modified date, themes/keywords, and downloadable resources (CSV files, data dictionaries). Use after search_datasets to inspect a dataset before pulling rows.