pierre_mcp_server
Verified Safeby Async-IO
Overview
Conversational AI fitness coaching and data analysis platform with provider integrations and user management.
Installation
cargo run --bin pierre-mcp-serverEnvironment Variables
- PIERRE_MASTER_ENCRYPTION_KEY
- DATABASE_URL
- CORS_ALLOWED_ORIGINS
- PIERRE_LLM_PROVIDER
- GEMINI_API_KEY
- GROQ_API_KEY
- LOCAL_LLM_API_KEY
- LOCAL_LLM_BASE_URL
- LOCAL_LLM_MODEL
- PIERRE_DISABLED_TOOLS
- PIERRE_JWT_SECRET
- HTTP_PORT
- RUST_LOG
Security Notes
The server is built with Rust, leveraging its memory safety features. It implements robust authentication (JWT, API Keys with constant-time comparison) and authorization. A two-tier key management system protects sensitive data at rest using AES256-GCM encryption with Additional Authenticated Data (AAD) for tenant/user isolation. OAuth2 flows include PKCE with S256 method enforced and atomic consumption of authorization codes/states to prevent replay and CSRF attacks. PII redaction is built into the logging middleware. Redirect URIs are strictly validated (HTTPS, no wildcards, no fragments). Client secrets are hashed using Argon2. No 'eval' or obvious malicious patterns found.
Similar Servers
garmin_mcp
Exposes Garmin Connect fitness and health data to Claude and other MCP-compatible clients.
intervals-mcp-server
Connects AI models (Claude, ChatGPT) with the Intervals.icu API to retrieve and manage athlete fitness data, including activities, events, and wellness metrics.
hevy-mcp
This server acts as a Model Context Protocol (MCP) interface, enabling AI assistants to interact with the Hevy fitness tracking app's API to manage workout data, routines, exercise templates, folders, and webhook subscriptions.
pierre_mcp_server
Conversational AI fitness coaching and data analysis platform with provider integrations and user management.