Connect Claude to Habito

Give Claude access to your Habito projects, tasks, and agents over MCP.

1. Get an API key

Every connection authenticates with a Bearer token of the form hab_*.

• Your user key lets Claude act as you.
• An agent key lets Claude act as that agent — its actions are recorded under the agent's name in the activity timeline. See Create an Agent for how to mint one.

Get a user key at habito.ar/profile → API Keys → Create new. Copy it now — you won't see it again.

2. Connect Claude

There are two ways to connect. Both authenticate with a hab_* Bearer token.

Option A — In-app endpoint (remote, recommended)

Habito serves an MCP endpoint over HTTP at https://habito.ar/mcp (powered by @nuxtjs/mcp-toolkit). Nothing to install — just point your client at it.

Claude Code:

claude mcp add --transport http habito https://habito.ar/mcp \
  --header "Authorization: Bearer hab_YOUR_KEY"

Claude Desktop — edit your config file:

# macOS
code ~/Library/Application\ Support/Claude/claude_desktop_config.json

# Windows
code %APPDATA%\Claude\claude_desktop_config.json

# Linux
code ~/.config/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "habito": {
      "transport": "http",
      "url": "https://habito.ar/mcp",
      "headers": {
        "Authorization": "Bearer hab_YOUR_KEY"
      }
    }
  }
}

Restart Claude Desktop.

This endpoint exposes 9 tools: list_projects, get_project, list_tasks, get_task, create_task, update_task, search_tasks, add_comment, get_me.

Option B — Standalone server (local, stdio)

A standalone MCP server lives in the repo at mcp-server/. Build it once:

cd mcp-server
bun install
bun run build

Then register it with your client, launching node mcp-server/dist/index.js and passing the key via env vars.

Claude Code:

claude mcp add habito \
  -e HABITO_API_KEY=hab_YOUR_KEY \
  -e HABITO_BASE_URL=https://habito.ar \
  -- node /absolute/path/to/mcp-server/dist/index.js

Claude Desktop:

{
  "mcpServers": {
    "habito": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-server/dist/index.js"],
      "env": {
        "HABITO_API_KEY": "hab_YOUR_KEY",
        "HABITO_BASE_URL": "https://habito.ar"
      }
    }
  }
}

The standalone server exposes 11 tools: the same 9 as above, plus create_project and list_teams.

3. Verify

Ask Claude:

"List my Habito projects"

If you see your projects, you're connected.

What Claude can do

With Habito connected, Claude can:

• Projects: list, view details (create, via the standalone server)
• Tasks: create, update, search, comment
• Teams: list (standalone server)
• Identity: check who it's acting as (get_me)

Example:

"Create a task in project HABITO titled 'Fix the login bug' with high priority"

Trouble? Check that:

1. The API key is copied correctly (no extra spaces) and prefixed with hab_
2. You restarted Claude after editing the config
3. For Option A, the Authorization header is set; for Option B, HABITO_API_KEY and HABITO_BASE_URL are set