Skip to main content

Connect Claude Code

Connect Claude Code to your team's MCP servers through Bloque in about five minutes. One HTTP endpoint replaces per-server local config.

1. Create a Bloque account​

Sign up at bloque.run with GitHub or email. A Hub is created for you automatically.

2. Add an MCP server​

Go to MCP Servers → Add Server and pick a server from the registry, paste a GitHub URL or npm package name, or enter connection details manually. See Add an MCP Server.

3. Generate an API key​

Open API Keys in the sidebar and create a key. Claude Code reads environment variables from the process that starts it, and there are three common ways to make BLOQUE_API_KEY available.

Option 1: Export the key in your shell​

Add this to your shell profile, such as ~/.zshrc or ~/.bashrc:

export BLOQUE_API_KEY="your Bloque API key"

Open a new terminal, then start Claude Code from that terminal.

Option 2: Use a .env wrapper​

If you keep the key in a project .env file:

BLOQUE_API_KEY="your Bloque API key"

Create a wrapper script such as bin/claude-with-env:

#!/usr/bin/env bash
set -euo pipefail

set -a
source .env
set +a

exec claude "$@"

Option 3: Read the key from an OS secret store​

Store the key in your operating system's managed keychain, then read it at launch time. For example, with cross-keychain:

#!/usr/bin/env bash
set -euo pipefail

export BLOQUE_API_KEY="$(cross-keychain get bloque BLOQUE_API_KEY)"
exec claude "$@"

4. Connect Claude Code​

Claude Code connects directly to the remote HTTP endpoint. You can configure it with a project-scoped .mcp.json file or with the claude mcp add command.

Option 1: .mcp.json​

Create or update .mcp.json in your project:

{
  "mcpServers": {
    "bloque": {
      "type": "http",
      "url": "https://mcp.bloque.run/mcp",
      "headers": {
        "Authorization": "Bearer ${BLOQUE_API_KEY}"
      }
    }
  }
}

Then launch Claude Code from a shell where BLOQUE_API_KEY is set.

Option 2: claude mcp add​

From your project directory:

claude mcp add --transport http --scope project bloque https://mcp.bloque.run/mcp \
  --header 'Authorization: Bearer ${BLOQUE_API_KEY}'

This writes a .mcp.json you can commit, so teammates get the same config — they only need their own BLOQUE_API_KEY:

{
  "mcpServers": {
    "bloque": {
      "type": "http",
      "url": "https://mcp.bloque.run/mcp",
      "headers": {
        "Authorization": "Bearer ${BLOQUE_API_KEY}"
      }
    }
  }
}

Verify:

claude mcp list

bloque should appear as connected.

See the Claude Code MCP documentation for more options.

5. Try it​

Start claude and run /mcp to see Bloque's status and tools, or just ask:

What tools do you have available from bloque?

Claude Code should list the tools from the servers you added in step 2.

What's next​