Skip to main content

Documentation Index

Fetch the complete documentation index at: https://hubify.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

​
Installation

npm install -g hubify-labs
Requires Node.js 18 or later. Installs both the hubify CLI and the hubify mcp launcher (which starts the Hubify MCP server for AI coding assistants).

​
Homebrew (macOS)

brew tap hubify/tap
brew install hubify

​
curl (Linux / macOS)

curl -fsSL https://get.hubify.com | sh
This downloads the latest binary and installs it to /usr/local/bin/hubify.

​
Verify Installation

hubify --version
You should see a version number printed (e.g. 1.0.0). If you get command not found, ensure your npm global bin directory is in your PATH (see Troubleshooting below).

​
Update

# npm
npm update -g hubify-labs

# Homebrew
brew upgrade hubify

# curl
curl -fsSL https://get.hubify.com | sh

​
Uninstall

# npm
npm uninstall -g hubify-labs

# Homebrew
brew uninstall hubify

# curl
rm /usr/local/bin/hubify

​
Using with Claude Code

After installing the CLI, add the Hubify MCP server to Claude Code so Claude can read and write your lab data directly.
The hubify mcp launcher is available in hubify-labs 2.0.0 and later. Run hubify --version to confirm your installed version is current.

​
Option A: claude mcp add (one command)

claude mcp add hubify -- hubify mcp
Then set your lab context: 
claude mcp add hubify \
  -e CONVEX_URL="https://your-deployment.convex.cloud" \
  -e HUBIFY_LAB_SLUG="your-lab-slug" \
  -- hubify mcp
Find your CONVEX_URL and lab slug under Settings → Developer in the Hubify web app.

​
Option B: manual ~/.claude/mcp.json

Create or merge into ~/.claude/mcp.json: 
{
  "mcpServers": {
    "hubify": {
      "command": "hubify",
      "args": ["mcp"],
      "env": {
        "CONVEX_URL": "https://your-deployment.convex.cloud",
        "HUBIFY_LAB_SLUG": "your-lab-slug"
      }
    }
  }
}

​
Verify Claude Code sees the server

Restart Claude Code, then run: 
claude mcp list
Expected line: hubify connected 48 tools Run the health check to confirm env resolution: 
hubify mcp --health
For the full Claude Code setup walkthrough, see MCP Setup.

​
Using with Codex

After installing the CLI: 
# Set env vars before starting Codex
export CONVEX_URL="https://your-deployment.convex.cloud"
export HUBIFY_LAB_SLUG="your-lab-slug"

# Point Codex at the MCP server
export CODEX_MCP_SERVERS='{"hubify":{"command":"hubify","args":["mcp"]}}'

codex
Or add to your Codex config file (~/.codex/config.json): 
{
  "mcpServers": {
    "hubify": {
      "command": "hubify",
      "args": ["mcp"],
      "env": {
        "CONVEX_URL": "https://your-deployment.convex.cloud",
        "HUBIFY_LAB_SLUG": "your-lab-slug"
      }
    }
  }
}

​
Requirements

RequirementVersion
Node.js18+ (for npm install)
Operating SystemmacOS, Linux, Windows (WSL)
TerminalAny terminal emulator
Shellbash, zsh, fish

​
Proxy / Firewall

If you are behind a corporate proxy: 
export HTTPS_PROXY=https://proxy.example.com:8080
hubify auth login
The CLI communicates with www.hubify.com/api over HTTPS (port 443).

​
Troubleshooting

Ensure your npm global bin directory is in your PATH:
export PATH="$(npm config get prefix)/bin:$PATH"
Avoid sudo npm install -g. Instead, configure npm to use a user directory:
mkdir ~/.npm-global
npm config set prefix '~/.npm-global'
export PATH=~/.npm-global/bin:$PATH
Use nvm to install a newer version:
nvm install 20
nvm use 20
npm install -g hubify-labs
  1. Confirm hubify mcp --health passes all checks
  2. Confirm hubify --version works (CLI is on PATH)
  3. Check that CONVEX_URL and HUBIFY_LAB_SLUG are set in your mcp.json env block
  4. Restart Claude Code — MCP servers are loaded at session start, not hot-reloaded