Connect to Claude & AI Tools (MCP)

BlinkLife supports MCP (Model Context Protocol), which lets external AI tools — like Claude, Cursor, and OpenClaw — securely connect to your BlinkLife account and work with your data and tools.

Connect in a few clicks (recommended)

Open Settings → MCP (Settings opens as an overlay from your profile menu)
Under MCP Keys, click the Create new key field
Pick your client from the Quick Connect list that appears:
- Claude Code
- Claude Desktop
- Cursor
- OpenClaw
BlinkLife creates a key and gives you a ready-to-paste command or config for that client — including the exact server URL. Follow the on-screen instructions.

Connect manually

If your tool isn’t in the Quick Connect list, create a key (Settings → MCP → Create new key, give it a name, then Create) and configure your client with:

Server URL: https://api.blinklife.com/api/v1/mcp
Transport: Streamable HTTP
Auth header: Authorization: Bearer YOUR_KEY

For example, with Claude Code:

claude mcp add --transport http blinklife https://api.blinklife.com/api/v1/mcp --header "Authorization: Bearer YOUR_KEY"

Claude Code: connecting and verifying

Claude Code talks to the server directly — no Node install, no config file to edit, no restart.

Connect

Paste the command from Quick Connect (or from Connect manually above) into your terminal:

claude mcp add --transport http blinklife https://api.blinklife.com/api/v1/mcp --header "Authorization: Bearer YOUR_KEY"

Claude Code writes the connection to ~/.claude.json and confirms it. Open Claude Code sessions pick it up immediately.

Verify

claude mcp list

You should see blinklife in the list. Then ask “list my BlinkLife tasks” in a Claude Code session — real data should come back.

Disconnect

Locally: claude mcp remove blinklife
Everywhere the key is used: Settings → MCP → Your keys → Revoke in BlinkLife — invalidates the key across every client, not just this machine

Claude Desktop: the server shows as failed

Quick Connect now generates the right config for your operating system, so most of this should not come up. If you hand-wrote your config, or the server still shows as failed, work through these in order.

1. Quit and reopen — properly

This is the most common cause by far. Claude Desktop reads the config file only when it starts, and closing the window does not quit the app.

macOS: press Cmd+Q, then reopen
Windows: right-click the Claude icon in the system tray (bottom-right, possibly under the ^ arrow) and choose Quit, then reopen

If your config is correct but nothing appears, it is almost always this.

2. The config must be one JSON object

If you already had an mcpServers entry, merge the BlinkLife block into it. Two objects pasted one after another is not valid JSON, and the whole file is ignored:

{
  "mcpServers": {
    "something-else": { "command": "..." },
    "blinklife": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.blinklife.com/api/v1/mcp", "--header", "Authorization: Bearer YOUR_KEY"]
    }
  }
}

3. Windows: the space in “Program Files”

Node installs to C:\Program Files\nodejs by default. The space splits the command, Windows only sees C:\Program, and the server shows as failed. Use the equivalent short path instead:

"blinklife": {
  "command": "C:\\PROGRA~1\\nodejs\\npx.cmd",
  "args": ["-y", "mcp-remote", "https://api.blinklife.com/api/v1/mcp", "--header", "Authorization: Bearer YOUR_KEY"]
}

Quick Connect already does this for you when it detects Windows.

4. Still failing? Check Node

The bridge needs Node.js installed locally. Run node --version in a terminal — if that fails, install Node and restart Claude Desktop.

Claude Desktop finds Node on its own in normal setups, including versions installed through nvm, asdf, fnm, or Homebrew, so you should not need to configure paths on macOS.

Claude Code, Cursor, and OpenClaw are unaffected — they connect to the server directly and don’t need Node at all.

Managing your keys

Your active keys are listed under Your keys in Settings → MCP. You can revoke a key at any time — the connection stops working immediately.

Keep your key safe

Treat your MCP key like a password — it grants access to your BlinkLife account. Don’t share it or paste it into public code. If a key is ever exposed, revoke it and create a new one.