Connect an AI assistant

FocusCrew as an MCP server: set-up for Claude Code, Cursor and Claude Desktop, and what an assistant can do.

FocusCrew is an MCP server (Model Context Protocol, Streamable HTTP) at https://www.focus-crew.com/api/mcp. Point an assistant at it with your key and it can list and write your to-dos, log habits, read and write notes, add flashcards and see what you are focusing on — through the same operations as the API, under the same limits. The tools are listed on MCP tools.

Set-up

Claude Code

claude mcp add --transport http focuscrew https://www.focus-crew.com/api/mcp \
  --header "Authorization: Bearer fc_live_…"

Cursor — .cursor/mcp.json

{
  "mcpServers": {
    "focuscrew": {
      "url": "https://www.focus-crew.com/api/mcp",
      "headers": { "Authorization": "Bearer fc_live_…" }
    }
  }
}

Claude.ai and the Claude desktop app — Settings → Connectors → Add custom connector

Name:            focus-crew
URL:             https://www.focus-crew.com/api/mcp
Authentication:  No sign-in   (the server uses an API key, not OAuth)
Request headers: Authorization = Bearer fc_live_…   (Required)

Claude Desktop, older builds — claude_desktop_config.json (through the mcp-remote bridge)

{
  "mcpServers": {
    "focuscrew": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://www.focus-crew.com/api/mcp", "--header", "Authorization: Bearer fc_live_…"]
    }
  }
}

Good to know

Any client that speaks MCP over HTTP with a custom header works the same way.
In Claude’s connector dialog pick No sign-in, even though it says it detected a sign-in: the server answers a missing key with a standard 401, which the dialog reads as OAuth. The key goes in a request header instead. ChatGPT’s connectors still need OAuth; that door is coming.
Nothing is kept between calls on our side — every request carries the key, so revoking it ends the connection at once.
The server tells the assistant to read before it writes, to say what it changed, and to ask before deleting.