vytalLink

VytalLink provides an MCP-compatible interface that surfaces personal health metrics from Apple HealthKit or Google Health Connect through a standalone Node.js MCP server. The server acts as an intermediary between your health data on-device and AI assistants or tooling that query the MCP API. Once the server is running, you can use it as a trusted data source for natural language prompts, enabling an AI assistant to ask for health insights such as activity trends, vitals summaries, or specific health metrics from your own device. The server is designed to be deployed outside the mobile app, allowing easy integration with cloud-hosted workflows or client-side tooling that consumes MCP endpoints. To interact with it, point your MCP-enabled client or prompt-engine at the server’s address and use standard MCP queries to request health data or derived insights.

Prerequisites:

• Node.js (LTS) installed on your machine
• npm or pnpm for package management
• Access to the repository (clone or download)

1. Clone the repository or download the mcp-server package:

• git clone <repository-url>
• cd vytalLink/mcp-server

2. Install dependencies:

• npm install

3. Configure environment (optional but recommended):

• Create a .env file or export environment variables as needed.
• Example: PORT=3000 NODE_ENV=development

4. Start the MCP server:

• npm run start or
• node index.js (or the path used in the project, e.g., node mcp-server/index.js)

5. Verify the server is running:

• Access http://localhost:3000/health or the configured port to confirm the server is up.

Note: If the project uses a different start script (e.g., npm run dev), use that command as documented in the mcp-server package.json.

Tips and considerations:

• The server relies on health data being accessible via Apple HealthKit or Google Health Connect; ensure the mobile app pairing is complete and permissions are granted.
• If you deploy behind a reverse proxy or in a cloud environment, configure CORS and authentication as needed for your use case.
• Common issues: port conflicts, missing environment variables, or misconfigured health data sources. Check server logs for details.
• Environment variables you might configure include PORT, NODE_ENV, and any health data source credentials required by the underlying connectors.
• If you plan to expose the MCP API publicly, consider enabling authentication and rate limiting to protect personal health data.