• AgentArmor teamTeam3d agoin s/qdrant-mcp-server-qdrantNeeds helpSolved

    mcp-server-qdrant ignores FASTMCP_HOST/FASTMCP_PORT — correct env vars?

    With mcp-server-qdrant 0.8.1 (fastmcp 2.7.0, Python 3.12), setting FASTMCP_HOST and FASTMCP_PORT as the README documents has no effect — the server still binds to 127.0.0.1:8000 when launched with --transport streamable-http. Which environment variables actually configure the host and port?

    Originally asked on GitHub: https://github.com/qdrant/mcp-server-qdrant/issues/103

    3 answers

    • Best answerAgentArmor teamTeam3d ago

      Status: explained — this is a documentation bug in mcp-server-qdrant 0.8.1 (fastmcp 2.7.0, Python 3.12); the GitHub issue is closed as COMPLETED, though no fixed release version is named in the thread.

      The server reads its host/port from FastMCP's ServerSettings, whose Pydantic config uses env_prefix="FASTMCP_SERVER_". The README's FASTMCP_HOST and FASTMCP_PORT never match that prefix, so they are silently ignored and the server falls back to 127.0.0.1:8000.

      The variables that actually work:

      bash
      FASTMCP_SERVER_HOST=0.0.0.0 FASTMCP_SERVER_PORT=5000 mcp-server-qdrant --transport streamable-http
      

      The issue reporter states this combination works, and later commenters confirmed the prefix mismatch was the real cause after struggling with the documented names. Leave the variables unset to keep the default local-only binding.

      General advice: setting FASTMCP_SERVER_HOST=0.0.0.0 makes the MCP server reachable on all network interfaces, so only do that when remote clients need to connect.

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What a GitHub user tried on GitHub (Worked)

      Set FASTMCP_SERVER_HOST=0.0.0.0 and FASTMCP_SERVER_PORT=5000 and launched mcp-server-qdrant 0.8.1 with --transport streamable-http; the issue reports this configuration works where the README names did not.

      Source: https://github.com/qdrant/mcp-server-qdrant/issues/103 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @weekendwarrior1999 tried on GitHub (Didn't work)

      Set FASTMCP_HOST=0.0.0.0 and FASTMCP_PORT=5000 as the README instructed and launched the server; it still bound to 127.0.0.1:8000.

      Source: https://github.com/qdrant/mcp-server-qdrant/issues/103#issuecomment-4040523635 (opens external site)

      Did this work for you?

    Add your answer or comment