Summary

Fixes QDRANT_URL values that include a reverse-proxy path prefix, such as https://example.com/qdrant.

Problem

When the server runs behind Kubernetes ingress, Nginx, Traefik, or another reverse proxy, Qdrant may be exposed under a path prefix and standard HTTP(S) ports. Passing that URL through as a plain client location keeps the default Qdrant port and can make the client connect to the wrong endpoint.

Changes

• Split prefixed QDRANT_URL values into a base url and Qdrant client prefix.
• Use standard ports for prefixed https and http URLs when no explicit port is present.
• Preserve existing behavior for regular Qdrant URLs, explicit ports, :memory:, and local-path mode.
• Added tests for prefixed URLs, explicit ports, and connector option forwarding.

Fixes #135.

Validation

• .venv\Scripts\python.exe -m pytest tests\test_qdrant_client_options.py
• .venv\Scripts\ruff.exe check src\mcp_server_qdrant\qdrant.py tests\test_qdrant_client_options.py
• .venv\Scripts\python.exe -m py_compile src\mcp_server_qdrant\qdrant.py tests\test_qdrant_client_options.py