Google Health Fitbit MCP vs Vaers
A side-by-side look at the Google Health Fitbit MCP and Vaers MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Google Health Fitbit MCP for biology & bioinformatics work as a local process; choose Vaers for biology & bioinformatics as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Google Health Fitbit MCP when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You want tools like
google_health_connection_status, google_health_quickstart, google_health_data_inventory.
Choose Vaers when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You want tools like
vaers_events_by_vaccine, vaers_events_by_symptom, vaers_coverage.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 57/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 19 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 18 | 3 |
| Full listing | View Google Health Fitbit MCP | View Vaers |
Tools & capabilities
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
Vaers tools 3
vaers_events_by_vaccineReport counts + severity breakdown by vaccine (and optionally manufacturer), for a year range. Omit `vaccine` to browse the top vaccines by report volume — this doubles as vax_type-code discovery.vaers_events_by_symptomReport-mention counts by symptom (MedDRA preferred term), optionally narrowed to one vaccine/year range. Omit `symptom` to see the most-reported symptoms.vaers_coverageTotal unique reports, year range, distinct vaccine/manufacturer counts, when the seed was last loaded, and the top 5 vaccines by volume.
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.
Google Health Fitbit MCP
{
"mcpServers": {
"google-health-fitbit-mcp": {
"command": "npx",
"args": [
"-y",
"google-health-fitbit-mcp"
]
}
}
}
Vaers
{
"mcpServers": {
"vaers": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-vaers"
]
}
}
}
Frequently asked questions
Google Health Fitbit MCP is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Vaers belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Google Health Fitbit MCP for biology & bioinformatics work and Vaers for biology & 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.
Google Health Fitbit MCP has no declared pricing — check the project's own site. Vaers 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 google-health-fitbit-mcp and vaers as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Health Fitbit MCP has a quality signal of 57/100 (Good) with 2 views, 0 installs and 19 GitHub stars. Vaers has 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars.