Withings MCP Server
by akutishevsky
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Server port (default: 3000) | 3000 |
| LOG_LEVEL | No | Logging level: trace, debug, info, warn, error (default: info) | info |
| SUPABASE_URL | Yes | Your Supabase project URL (from Dashboard → Settings → API) | |
| ALLOWED_ORIGINS | No | Comma-separated list of allowed CORS origins for browser clients | |
| ENCRYPTION_SECRET | Yes | 32+ character secret for token encryption (generate with `bun run generate-secret`) | |
| WITHINGS_CLIENT_ID | Yes | Your Withings app client ID | |
| SUPABASE_SECRET_KEY | Yes | Your Supabase service role key (from Dashboard → Settings → API) | |
| WITHINGS_REDIRECT_URI | Yes | OAuth callback URL (must match Withings app settings) | |
| WITHINGS_CLIENT_SECRET | Yes | Your Withings app client secret |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/akutishevsky/withings-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server