You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Port configuration support for Fleet MCP: The Fleet MCP server now dynamically respects the --port CLI argument and the FLEET_MCP_PORT environment variable at runtime. This fixes previous issues where the environment variable was ignored in Docker or CLI usage. You can set the port for HTTP-based transports (SSE and streamable-http) in any of the following ways:
fleet-mcp run --port 8001 (CLI argument takes precedence)
FLEET_MCP_PORT=8001 fleet-mcp run (environment variable is used if no CLI argument is given)
If neither is set, the default is port 8000.
This ensures correct port selection in Docker, Docker Compose, and all deployment scenarios.
SSE (Server-Sent Events) transport support: Fleet MCP now supports the sse transport, allowing real-time event streaming and compatibility with MCP clients that use SSE.
Changed
The Docker Compose and environment setup can now map any desired port to the Fleet MCP container, and the server will listen on the configured port.
See the README for usage details and updated configuration examples.
Thank you for sharing your pull request. After reviewing the PR, there's a couple of questions that came up:
I do see a use case for specifying the port that the MCP server listens on. I could see port conflicts happening so that's useful especially if you're running other docker containers. Could you change the default network binding address from 0.0.0.0 to 127.0.0.1? This will at least prevent accidental exposure if anyone were to spin up this MCP server without being aware of this configuration. We could also set this as an environment variable/argument just for additional flexibility but would like to still default to localhost only out of the box unless the user explicitly wants to expose it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added
--portCLI argument and theFLEET_MCP_PORTenvironment variable at runtime. This fixes previous issues where the environment variable was ignored in Docker or CLI usage. You can set the port for HTTP-based transports (SSE and streamable-http) in any of the following ways:fleet-mcp run --port 8001(CLI argument takes precedence)FLEET_MCP_PORT=8001 fleet-mcp run(environment variable is used if no CLI argument is given)ssetransport, allowing real-time event streaming and compatibility with MCP clients that use SSE.Changed
See the README for usage details and updated configuration examples.