Data Brussels vs Server Everything
A side-by-side look at the Data Brussels and Server Everything MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Data Brussels for data platforms work as a local process; choose Server Everything for other tools and integrations as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Data Brussels 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 Server Everything when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
echo, get-annotated-message, get-env.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Platforms | Other Tools and Integrations |
| Quality signal | 59/100 · Good | 73/100 · Great |
| 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 | Community listing |
| GitHub stars | 0 | 91,547 |
| Directory activity | 1 views 0 installs 0 upvotes | 10 views 0 installs 0 upvotes |
| Tools | 3 | 16 |
| Full listing | View Data Brussels | View Server Everything |
Tools & capabilities
Data Brussels tools 3
search_datasetsSearch Brussels Open Data for datasets by keyword (city services, mobility, culture & urban data). Returns dataset_ids (pass to query/dataset_info), titles, themes and record counts.dataset_infoGet metadata for one Brussels Open Data dataset (fields/schema, themes, record count) — call before query to learn the column names.queryQuery records from a Brussels Open Data dataset with ODSQL. Filter (where), aggregate (group_by/select), sort (order_by), paginate (limit/offset).
Server Everything tools 16
echoEchoes back the input stringget-annotated-messageDemonstrates how annotations can be used to provide metadata about content.get-envReturns all environment variables, helpful for debugging MCP server configurationget-header-paramsReturns its region argument and the Mcp-Param-Region HTTP header it arrived in. Demonstrates x-mcp-header (a 2026-07-28 Streamable HTTP client mirrors the argument into the header) and JSON Schema 2020-12 input and output schemas.get-resource-linksReturns up to ten resource links that reference different types of resourcesget-resource-referenceReturns a resource reference that can be used by MCP clientsget-structured-contentReturns structured content along with an output schema for client data validationget-sumReturns the sum of two numbersget-tiny-imageReturns a tiny MCP logo image.gzip-file-as-resourceCompresses a single file using gzip compression. Depending upon the selected output type, returns either the compressed data as a gzipped resource or a resource link, allowing it to be downloaded in a subsequent request: during the current session for a 2025-era client, or for ten minutes at a minted URI on protocol version 2026-07-28.trigger-list-changedSends a notifications/<list>/list_changed for the tool, prompt or resource list. On protocol version 2026-07-28 it is delivered on each subscriptions/listen stream that asked for that list; a 2025-era client receives it unsolicited.trigger-log-messagesSends one log message at each logging level during the call. On protocol version 2026-07-28 only the messages at or above the level the request names in _meta (io.modelcontextprotocol/logLevel) are sent, and none if it names no level; a 2025-era client gets those at or above the level it set with logging/setLevel. Deprecated: logging is deprecated as of protocol version 2026-07-28.- +4 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 Brussels
{
"mcpServers": {
"data-brussels": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-data-brussels"
]
}
}
}
Server Everything
{
"mcpServers": {
"modelcontextprotocol-server-everything": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-everything"
]
}
}
}
Frequently asked questions
Data Brussels is categorized under Data Platforms and uses a local stdio subprocess. Server Everything belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick Data Brussels for data platforms work and Server Everything for other tools and integrations.
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 Brussels has no declared pricing — check the project's own site. Server Everything 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-brussels and modelcontextprotocol-server-everything as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Data Brussels has a quality signal of 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Server Everything has 73/100 (Great) with 10 views, 0 installs and 91,547 GitHub stars.