MCP Setup

This guide walks you through installing the Hubify MCP server and connecting it to your AI coding assistant.

Installation

npm install -g @hubify/mcp-server

Configuration

Claude Code

Add the Hubify MCP server to your Claude Code configuration:

// ~/.claude/mcp_servers.json
{
  "hubify": {
    "command": "hubify-mcp",
    "args": ["--lab", "bigbounce"],
    "env": {
      "HUBIFY_API_KEY": "hfy_key_abc123..."
    }
  }
}

Cursor

Add to your Cursor MCP configuration:

// .cursor/mcp.json
{
  "mcpServers": {
    "hubify": {
      "command": "hubify-mcp",
      "args": ["--lab", "bigbounce"],
      "env": {
        "HUBIFY_API_KEY": "hfy_key_abc123..."
      }
    }
  }
}

Generic MCP Host (SSE)

For hosts that support Server-Sent Events transport:

hubify-mcp --transport sse --port 3100 --lab bigbounce

Connect your MCP host to http://localhost:3100/sse.

Options

Option	Default	Description
--lab <slug>	Default lab	Target lab
--transport <type>	stdio	Transport: stdio or sse
--port <n>	3100	Port for SSE transport
--verbose	false	Enable debug logging

Environment Variables

Variable	Required	Description
HUBIFY_API_KEY	Yes	Your Hubify API key
HUBIFY_LAB	No	Default lab slug (overridden by --lab)
HUBIFY_API_URL	No	API base URL (default: https://api.hubify.com/v1)

Verifying the Setup

Once configured, test from your AI assistant:

Ask: "What experiments are running in my lab?"

The assistant should be able to call the hubify_experiment_list tool and return real data from your lab.

You can also test directly:

hubify mcp test

MCP Server: @hubify/mcp-server v1.0.0
Connection: OK
Lab: bigbounce
Tools: 18 available
Resources: 6 resource types
Prompts: 5 available

Troubleshooting

<AccordionGroup>

Server not found

Ensure the hubify-mcp binary is in your PATH:

which hubify-mcp

If not found, reinstall: npm install -g @hubify/mcp-server

Authentication failed

Verify your API key:

hubify auth status

Regenerate if needed: hubify auth api-key create --name "mcp" --scope "*"

No tools showing in assistant

Check that the MCP configuration file path is correct for your assistant. Restart the assistant after adding the configuration.

</AccordionGroup>