connect-self-hosted-https

Connect the infracodebase MCP server to a self-hosted HTTPS API

The server takes all configuration from environment variables (or flags) supplied by the MCP client — there is no init, no auth login, and no stored config file. Connecting to a self-hosted instance means setting two (sometimes three) env vars in the client's server definition.

The variables

Variable	Purpose	Required
INFRACODEBASE_TOKEN	Personal access token (icb_pat_...)	Yes
INFRACODEBASE_API_URL	Your instance's API base, e.g. https://infra.acme.com/api/v1	Yes for self-hosted (defaults to the SaaS)
NODE_EXTRA_CA_CERTS	Path to your CA cert — only for HTTPS with a private/self-signed cert	Only if TLS fails

Step 1 — point at your instance

Use the --env flag (repeatable) on claude mcp add. The -- separates Claude's flags from the command that launches the server.

Via npx (published package):

claude mcp add infracodebase \
  --env INFRACODEBASE_TOKEN=icb_pat_xxx \
  --env INFRACODEBASE_API_URL=https://infra.acme.com/api/v1 \
  -- npx -y @infracodebase/mcp@latest

From a local clone (after npm install && npm run build):

claude mcp add infracodebase \
  --env INFRACODEBASE_TOKEN=icb_pat_xxx \
  --env INFRACODEBASE_API_URL=https://localhost:3000/api/v1 \
  -- node /abs/path/to/infracodebase-mcp/dist/index.js

Equivalent mcp.json (Claude Desktop / Cursor / etc.):

{
  "mcpServers": {
    "infracodebase": {
      "command": "npx",
      "args": ["-y", "@infracodebase/mcp@latest"],
      "env": {
        "INFRACODEBASE_TOKEN": "icb_pat_xxx",
        "INFRACODEBASE_API_URL": "https://infra.acme.com/api/v1"
      }
    }
  }
}

Add --scope user (or set it in user config) to make the server available across all projects instead of just the current one.

Step 2 — handle the certificate (HTTPS only)

Plain http:// (e.g. http://localhost:3000) needs nothing further — skip this step.