fix: Fix MCP server host and transport in Docker environment #86
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.
Here are the changes:
FASTMCP_HOST
env wasn't working for me, and the MCP server was not listening on 0.0.0.0 (which was important in Docker container so I can access it from the outside). I couldn't even find usage ofFASTMCP_HOST
in the Fast MCP GitHub repo. I've changed it toMCP_HOST
to be aligned withMCP_TRANSPORT
(no mention of fast).streamable-http
is the default, butstdio
was the default. I've fixed it to match the docs, havingstreamable-http
as default.