Gevety MCP Server
MCP (Model Context Protocol) server for Gevety Health, enabling Claude Desktop to access your blood test results, wearable data, and health insights.
Quick Setup (All Platforms)
# One-line setup for Claude Desktop, Claude Code, and Clawdbot
curl -sSL https://raw.githubusercontent.com/gevety/mcp-server/main/scripts/setup-ai-assistant.sh | bash
The script will:
- Prompt for your API token (get it at gevety.com/settings)
- Detect installed AI platforms
- Configure each platform automatically
Features
- list_available_data - Discover available biomarkers, wearables, and date ranges
- get_health_summary - Get overall healthspan score and top concerns
- query_biomarker - Query specific biomarker history and trends
- get_wearable_stats - Get aggregated wearable metrics (Garmin, Oura, Whoop)
Installation
# Install with pip
pip install gevety-mcp
# Or install from source
git clone https://github.com/gevety/mcp-server
cd mcp-server
pip install -e .
Quick Start
1. Get an API Token
- Log in to Gevety
- Go to Settings → Developer API
- Click Generate Token
- Copy the token (starts with
gvt_)
2. Configure Claude Desktop
Add to your Claude Desktop config (claude_desktop_config.json):
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"gevety": {
"command": "gevety-mcp",
"env": {
"GEVETY_API_TOKEN": "gvt_your_token_here"
}
}
}
}
3. Restart Claude Desktop
After saving the config, restart Claude Desktop. You should see "gevety" in the MCP servers list.
Usage Examples
Once configured, you can ask Claude about your health data:
"What biomarkers do I have data for?"
"Show me my health summary"
"How is my vitamin D trending?"
"What are my average steps this month?"
"Query my cholesterol history"
Environment Variables
| Variable | Required | Description |
|---|---|---|
GEVETY_API_TOKEN |
Yes | Your Gevety API token (gvt_xxx) |
GEVETY_API_URL |
No | API base URL (defaults to production) |
Development
# Install dev dependencies
pip install -e ".[dev]"
# Run tests
pytest
# Run server locally
GEVETY_API_TOKEN=gvt_xxx gevety-mcp
API Endpoints
The MCP server calls these Gevety API endpoints:
GET /api/v1/mcp/tools/list_available_dataGET /api/v1/mcp/tools/get_health_summaryGET /api/v1/mcp/tools/query_biomarker?biomarker=xxx&days=365GET /api/v1/mcp/tools/get_wearable_stats?days=30
All endpoints require Bearer token authentication and support caching.
Response Headers
| Header | Description |
|---|---|
X-Gevety-Cache-Hit |
Whether response was served from cache |
X-Gevety-Data-Age |
Seconds since data was computed |
X-RateLimit-Limit |
Request limit per minute |
X-RateLimit-Remaining |
Remaining requests |
X-RateLimit-Reset |
Unix timestamp when limit resets |
Rate Limits
- 100 requests/minute
- 1,000 requests/hour
- 10,000 requests/day
Other AI Platforms
Clawdbot
For Clawdbot users, we provide an AgentSkills-compatible skill instead of MCP:
# Copy the skill to your Clawdbot skills directory
mkdir -p ~/.clawdbot/skills/gevety
cp src/gevety_mcp/skills/clawdbot/SKILL.md ~/.clawdbot/skills/gevety/
Configure in ~/.clawdbot/clawdbot.json:
{
"skills": {
"entries": {
"gevety": {
"enabled": true,
"env": {
"GEVETY_API_TOKEN": "gvt_your_token_here"
}
}
}
}
}
See src/gevety_mcp/skills/README.md for details.
ChatGPT / Other Platforms
The underlying REST API is platform-agnostic. See API Endpoints above for direct integration.
Privacy
- All data access is read-only
- Your data never leaves Gevety's servers
- API tokens can be revoked anytime from Settings
- See Privacy Policy
License
MIT License - see LICENSE file.
Support
Metadata
Release files for gevety-mcp 0.12.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gevety_mcp-0.12.0.tar.gz | 37.6 kB | Without provenance | Details for gevety_mcp-0.12.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gevety_mcp-0.12.0-py3-none-any.whl | Python 3 | none | any | Details for gevety_mcp-0.12.0-py3-none-any.whl |
Total release size: 76.4 kB
Release files / gevety_mcp-0.12.0.tar.gz
| Download URL | gevety_mcp-0.12.0.tar.gz |
|---|---|
| Size | 37.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa05aa0b4314082ff6e8ff78d6adb14275a73f936b3eb4babe2f29b28c879444
|
|
BLAKE2b-256 checksum How to use checksums |
675a2bcc9ce12ba9d4cb85800550393db6767c25907d33d0680c8622545fa0d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.16 {"installer":{"name":"uv","version":"0.12.16","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / gevety_mcp-0.12.0-py3-none-any.whl
| Download URL | gevety_mcp-0.12.0-py3-none-any.whl |
|---|---|
| Size | 38.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b68575234da7a01b83894c1e286e9ec30e6e52260ad6ce8ee727040f1f329ac2
|
|
BLAKE2b-256 checksum How to use checksums |
fdbace14773da7c08865fbff4b524a0778e87ec37e88f943795ab0df9408eaa4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.16 {"installer":{"name":"uv","version":"0.12.16","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for gevety-mcp 0.12.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.