Skip to content

more flexible payload schema? #81

@azhang

Description

@azhang

I see in the code that this mcp is hardcoded to read from payload and metadata fields. Am I correct in understanding that this MCP server only works for collections that have those fields? Is there any plan to make this support more use cases? For example even the examples on qdrant's website https://qdrant.tech/documentation/concepts/payload/ aren't queryable using this mcp

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions