Connect Cursor & VS Code

Agentic coding tools — Cursor, VS Code (with GitHub Copilot), and others like JetBrains IDEs and Windsurf — can connect to Hemix as a remote MCP server. The connector URL is https://mcp.hemix.life/mcp, and each opens a browser window for sign-in on first connect.

VS Code (GitHub Copilot)

Requires VS Code 1.101 or later (remote MCP + OAuth). MCP servers live in an mcp.json file — root key servers:

``json { "servers": { "hemix": { "type": "http", "url": "https://mcp.hemix.life/mcp" } } } ``

On first use, VS Code opens a browser window to sign in to Hemix and authorize. Then use it from Copilot Chat in agent mode.

Cursor

Open Settings → MCP → Add server (or edit ~/.cursor/mcp.json). Cursor uses the mcpServers key:

``json { "mcpServers": { "hemix": { "url": "https://mcp.hemix.life/mcp" } } } ``

Cursor handles the OAuth sign-in in your browser on first connect.

Tools that only run *local* servers

If a tool only accepts a command to launch (a local/stdio server) rather than a URL, point it at Hemix with the mcp-remote bridge:

``json { "mcpServers": { "hemix": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.hemix.life/mcp"] } } } ``

The bridge opens the Hemix sign-in in your browser and relays the connection.

*Menu names and config formats change between versions — when in doubt, check your tool's own MCP docs and use the connector URL https://mcp.hemix.life/mcp. Hemix exports your stored record, never a Hemix-computed interpretation. Hemix is a wellness tracking tool, not a medical device.*