MCP Server Setup

Claude Code supports MCP servers natively via the CLI or a project config file.

Option 1: CLI command

claude mcp add --transport http flameon \
  --header "Authorization: Bearer YOUR_TOKEN" \
  --header "X-Application: your-team-slug/your-app-slug" \
  https://flameon.ai/mcp

Option 2: Project config (.mcp.json)

Create .mcp.json in your project root:

{
  "mcpServers": {
    "flameon": {
      "type": "http",
      "url": "https://flameon.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${FLAMEON_API_KEY}",
        "X-Application": "your-team-slug/your-app-slug"
      }
    }
  }
}

Use ${FLAMEON_API_KEY} in place of the token value to read from the FLAMEON_API_KEY environment variable.

Codex uses a TOML config file with native streamable HTTP support.

Edit ~/.codex/config.toml

[mcp_servers.flameon]
url = "https://flameon.ai/mcp"
bearer_token_env_var = "FLAMEON_API_KEY"

[mcp_servers.flameon.headers]
X-Application = "your-team-slug/your-app-slug"

Then set the environment variable:

export FLAMEON_API_KEY="your-api-key-here"

Or via CLI

codex mcp add flameon --url https://flameon.ai/mcp

Then edit ~/.codex/config.toml to add bearer_token_env_var and the X-Application header.

Gemini CLI supports streamable HTTP via the httpUrl field.

Option 1: CLI command

gemini mcp add --transport http flameon \
  https://flameon.ai/mcp \
  --header "Authorization: Bearer YOUR_TOKEN" \
  --header "X-Application: your-team-slug/your-app-slug"

Option 2: Edit ~/.gemini/settings.json

{
  "mcpServers": {
    "flameon": {
      "httpUrl": "https://flameon.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${FLAMEON_API_KEY}",
        "X-Application": "your-team-slug/your-app-slug"
      }
    }
  }
}

Use ${FLAMEON_API_KEY} in place of the token value to read from the FLAMEON_API_KEY environment variable.

Amp (by Sourcegraph) uses streamable HTTP by default for remote MCP servers.

Edit ~/.config/amp/settings.json

{
  "amp.mcpServers": {
    "flameon": {
      "url": "https://flameon.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${FLAMEON_API_KEY}",
        "X-Application": "your-team-slug/your-app-slug"
      }
    }
  }
}

For project-scoped config, create .amp/settings.json in your project root (requires approval on first run).

Use ${FLAMEON_API_KEY} in place of the token value to read from the FLAMEON_API_KEY environment variable.

OpenCode supports remote MCP servers with custom headers.

Edit opencode.json

Place in your project root or ~/.config/opencode/opencode.json for global config:

{
  "mcp": {
    "flameon": {
      "type": "remote",
      "url": "https://flameon.ai/mcp",
      "headers": {
        "Authorization": "Bearer {env:FLAMEON_API_KEY}",
        "X-Application": "your-team-slug/your-app-slug"
      },
      "oauth": false,
      "enabled": true
    }
  }
}

Use {env:FLAMEON_API_KEY} in place of the token value to read from the FLAMEON_API_KEY environment variable.

Cursor auto-detects streamable HTTP when you provide a url field.

Edit .cursor/mcp.json

Create in your project root or ~/.cursor/mcp.json for global:

{
  "mcpServers": {
    "flameon": {
      "url": "https://flameon.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${env:FLAMEON_API_KEY}",
        "X-Application": "your-team-slug/your-app-slug"
      }
    }
  }
}

Use ${env:FLAMEON_API_KEY} in place of the token value to read from the FLAMEON_API_KEY environment variable.

Windsurf uses serverUrl for HTTP-based MCP servers.

Edit ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "flameon": {
      "serverUrl": "https://flameon.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${env:FLAMEON_API_KEY}",
        "X-Application": "your-team-slug/your-app-slug"
      }
    }
  }
}

Use ${env:FLAMEON_API_KEY} in place of the token value to read from the FLAMEON_API_KEY environment variable.

Zed configures MCP servers under context_servers in its settings file.

Edit ~/.config/zed/settings.json

{
  "context_servers": {
    "flameon": {
      "url": "https://flameon.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN",
        "X-Application": "your-team-slug/your-app-slug"
      }
    }
  }
}

If your build of Zed doesn't support native HTTP yet, use mcp-remote as a proxy:

{
  "context_servers": {
    "flameon": {
      "command": {
        "path": "npx",
        "args": [
          "-y", "mcp-remote",
          "https://flameon.ai/mcp",
          "--header",
          "Authorization:Bearer YOUR_TOKEN",
          "--header",
          "X-Application:your-team-slug/your-app-slug"
        ]
      }
    }
  }
}

FlameOn's MCP server implements the MCP Streamable HTTP transport (spec version 2025-03-26). Any MCP-compatible client can connect.

Connection details

Using mcp-remote as a stdio bridge

If your agent only supports stdio-based MCP servers, use mcp-remote to bridge:

npx -y mcp-remote https://flameon.ai/mcp \
  --header "Authorization: Bearer YOUR_TOKEN" \
  --header "X-Application: your-team-slug/your-app-slug"

Point your agent's MCP config at this command using its stdio/local transport type.