Nimbus BCI vs Google Health Fitbit MCP
A side-by-side look at the Nimbus BCI and Google Health Fitbit MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
N
Nimbus BCIBiology, Medicine and Bioinformatics · Local subprocess (stdio)AI agents build, train, and analyze BCI/EEG pipelines: data, models, experiments, live sessions.43FairAuth: oauth 2.0Verdict: choose Nimbus BCI for biology, medicine and bioinformatics work as a local process; choose Google Health Fitbit MCP for biology, medicine and bioinformatics as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
NChoose Nimbus BCI when
- You need dedicated capabilities in the Biology, Medicine and Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
NIMBUS_API_URL, NIMBUS_TOKEN, NIMBUS_TOKEN_FILE, NIMBUS_MCP_KEY, NIMBUS_MCP_KEY_FILE, MCP_LOCAL_KEY, MCP_LOCAL_USER_ID, HOST.
Choose Google Health Fitbit MCP when
- You need dedicated capabilities in the Biology, Medicine and Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You want tools like
google_health_connection_status, google_health_quickstart, google_health_data_inventory.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | N Nimbus BCI | |
|---|---|---|
| Category | Biology, Medicine and Bioinformatics | Biology, Medicine and Bioinformatics |
| Quality signal | 43/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | NIMBUS_API_URLNIMBUS_TOKENNIMBUS_TOKEN_FILENIMBUS_MCP_KEYNIMBUS_MCP_KEY_FILEMCP_LOCAL_KEYMCP_LOCAL_USER_IDHOST | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 17 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 18 |
| Full listing | View Nimbus BCI | View Google Health Fitbit MCP |
Tools & capabilities
Nimbus BCI tools
No tool names declared yet. Check the project README from the listing page.
Google Health Fitbit MCP tools 18
google_health_connection_statusLocal config, token, scope and MCP-client readiness — no Google callgoogle_health_quickstartPersonalized 3-step setup walkthrough that adapts to your current stategoogle_health_data_inventorySupported domains, scopes, data-type naming and recommended agent flowgoogle_health_list_data_typesThe 39 kebab-case data-type slugs with units, scopes and supported verbsgoogle_health_demoRealistic synthetic payloads so agents see the contract before real callsgoogle_health_get_identity/v4/users/me/identity` — Google Health + legacy Fitbit identity mappinggoogle_health_get_profile/v4/users/me/profilegoogle_health_get_settings/v4/users/me/settings` — units, timezonegoogle_health_list_paired_devices/v4/users/me/pairedDevices` — your Fitbit trackers and Pixel Watches, and which device produces which datagoogle_health_get_irn_profile/v4/users/me/irnProfile` — irregular-rhythm (AFib) notification engagement statusgoogle_health_list_data_points/v4/.../dataPoints` — intraday detail for any data typegoogle_health_get_data_point/v4/.../dataPoints/{id}` — one specific sleep session, exercise or measurement- +6 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.
Nimbus BCI
{
"mcpServers": {
"nimbus-bci": {
"command": "uvx",
"args": [
"nimbus-mcp"
],
"env": {
"NIMBUS_API_URL": "YOUR_NIMBUS_API_URL_HERE",
"NIMBUS_TOKEN": "YOUR_NIMBUS_TOKEN_HERE",
"NIMBUS_TOKEN_FILE": "YOUR_NIMBUS_TOKEN_FILE_HERE",
"NIMBUS_MCP_KEY": "YOUR_NIMBUS_MCP_KEY_HERE",
"NIMBUS_MCP_KEY_FILE": "YOUR_NIMBUS_MCP_KEY_FILE_HERE",
"MCP_LOCAL_KEY": "YOUR_MCP_LOCAL_KEY_HERE",
"MCP_LOCAL_USER_ID": "YOUR_MCP_LOCAL_USER_ID_HERE",
"HOST": "YOUR_HOST_HERE"
}
}
}
}
Google Health Fitbit MCP
{
"mcpServers": {
"google-health-fitbit-mcp": {
"command": "npx",
"args": [
"-y",
"google-health-fitbit-mcp"
]
}
}
}
Frequently asked questions
Nimbus BCI is categorized under Biology, Medicine and Bioinformatics and uses a local stdio subprocess. Google Health Fitbit MCP belongs to Biology, Medicine and Bioinformatics and uses a local stdio subprocess. Pick Nimbus BCI for biology, medicine and bioinformatics work and Google Health Fitbit MCP for biology, medicine and bioinformatics.
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.
Nimbus BCI has no declared pricing — check the project's own site. Auth: oauth 2.0. Google Health Fitbit MCP has no declared pricing — check the project's own site. 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 nimbus-bci and google-health-fitbit-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Nimbus BCI has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 3 GitHub stars. Google Health Fitbit MCP has 57/100 (Good) with 0 views, 0 installs and 17 GitHub stars.