farhoodlabs/devcontainer
8
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 39 Wiki Activity

fix(chart): homeassistant-mcp sidecar uses wrong fastmcp CLI flags #26

New Issue
Closed
opened 2026-02-21 16:13:26 +00:00 by cpfarhood · 1 comment
cpfarhood commented 2026-02-21 16:13:26 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Problem

The homeassistant-mcp sidecar container command uses --sse-server-host and --sse-server-port flags which are not valid for the current version of fastmcp (bundled in ghcr.io/homeassistant-ai/ha-mcp:6.7.1).

This causes the sidecar to crash with:

Unknown option: "--sse-server-host". Did you mean "--server-spec"?

Current command

fastmcp run ha_mcp.main:app --transport sse --sse-server-host 0.0.0.0 --sse-server-port 8087

Expected command

fastmcp run ha_mcp.main:app --transport sse --host 0.0.0.0 --port 8087

The correct flags per fastmcp run --help are:

  • --host (not --sse-server-host)
  • --port / -p (not --sse-server-port)

Affected file

chart/templates/deployment.yaml — the homeassistant-mcp sidecar command block.

Additional context

  • Chart version: 0.2.0
  • Image: ghcr.io/homeassistant-ai/ha-mcp:6.7.1
  • The image tag fix from v6.7.1 → 6.7.1 was resolved in 0.2.0
## Problem The homeassistant-mcp sidecar container command uses `--sse-server-host` and `--sse-server-port` flags which are not valid for the current version of fastmcp (bundled in `ghcr.io/homeassistant-ai/ha-mcp:6.7.1`). This causes the sidecar to crash with: ``` Unknown option: "--sse-server-host". Did you mean "--server-spec"? ``` ## Current command ``` fastmcp run ha_mcp.main:app --transport sse --sse-server-host 0.0.0.0 --sse-server-port 8087 ``` ## Expected command ``` fastmcp run ha_mcp.main:app --transport sse --host 0.0.0.0 --port 8087 ``` The correct flags per `fastmcp run --help` are: - `--host` (not `--sse-server-host`) - `--port` / `-p` (not `--sse-server-port`) ## Affected file `chart/templates/deployment.yaml` — the homeassistant-mcp sidecar `command` block. ## Additional context - Chart version: 0.2.0 - Image: `ghcr.io/homeassistant-ai/ha-mcp:6.7.1` - The image tag fix from `v6.7.1` → `6.7.1` was resolved in 0.2.0
cpfarhood commented 2026-02-21 16:25:22 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Update — additional findings from v0.2.1

The --host/--port fix alone isn't sufficient. The fastmcp run ha_mcp.main:app approach doesn't work because:

  1. The module path ha_mcp.main doesn't exist — it's ha_mcp.__main__
  2. The app object is a deferred proxy (_DeferredMCP), not directly runnable via fastmcp run

Correct approach

The ha-mcp image provides built-in CLI entrypoints (defined in pyproject.toml):

  • ha-mcp — stdio transport (default)
  • ha-mcp-sse — SSE transport on port 8087
  • ha-mcp-web — HTTP streamable transport on port 8086
  • ha-mcp-oauth — OAuth mode

The chart should use:

command: ["ha-mcp-sse"]
args: []  # no args needed, defaults to 0.0.0.0:8087

Port and path can be configured via env vars:

  • MCP_PORT (default: 8087 for SSE)
  • MCP_SECRET_PATH (default: /mcp)

No fastmcp run wrapper needed.

## Update — additional findings from v0.2.1 The `--host`/`--port` fix alone isn't sufficient. The `fastmcp run ha_mcp.main:app` approach doesn't work because: 1. The module path `ha_mcp.main` doesn't exist — it's `ha_mcp.__main__` 2. The app object is a deferred proxy (`_DeferredMCP`), not directly runnable via `fastmcp run` ### Correct approach The ha-mcp image provides built-in CLI entrypoints (defined in pyproject.toml): - `ha-mcp` — stdio transport (default) - `ha-mcp-sse` — SSE transport on port 8087 - `ha-mcp-web` — HTTP streamable transport on port 8086 - `ha-mcp-oauth` — OAuth mode The chart should use: ```yaml command: ["ha-mcp-sse"] args: [] # no args needed, defaults to 0.0.0.0:8087 ``` Port and path can be configured via env vars: - `MCP_PORT` (default: 8087 for SSE) - `MCP_SECRET_PATH` (default: `/mcp`) No `fastmcp run` wrapper needed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
antigravity
architecture
automation
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 examples
good first issue
Good for newcomers
 helm
help wanted
Extra attention is needed
 invalid
This doesn't seem right
 maintainability
monitoring
question
Further information is requested
 refactor
tooling
user-experience
validation
wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
fl_blake (Blake MIddleware) cpfarhood (Chris Farhood) ci (Continuous Integration [bot]) flux (Flux CD) admin (Gitea Admin) fl_hugh (Hugh Commit) renovate (Mend Renovate) fl_warren (Warren Bufferpool)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: farhoodlabs/devcontainer#26
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?