Summary

Add a focused regression test for qdrant-store so storing content without a metadata argument stays supported. The test drives the server through a real FastMCP client and verifies the connector still receives metadata=None.

Why it matters

src/mcp_server_qdrant/mcp_server.py already documents that the metadata parameter shape is client-sensitive, especially for MCP clients such as Cursor. Without coverage, a refactor can silently make metadata required or stop passing None, breaking normal store calls from clients that omit the field.

Testing

Added tests/test_mcp_server.py with an async regression test that instantiates QdrantMCPServer against a mocked connector and calls qdrant-store through fastmcp.Client. The assertion checks both the returned confirmation message and that the stored Entry still carries metadata=None.