Skip to main content

Qdrant Vector DB MCP

Run vector operations against Qdrant through the MAD MCP broker with configurable ingest workflows for documents and textbooks.

Authentication​

  • Header: Authorization

  • Format: Bearer mad_live_***

  • Configure Qdrant URL + API key in Integrations before using broker tools.

  • Use qdrant-ingest-textbook for large textbook workflows (async job pipeline).

  • Use qdrant-ingest-document for non-textbook document/content ingestion.

Catalog Coverage​

  • Raw provider tools: 80
  • Exposed compatibility tools: 80
  • Agent-ready tools: 72
  • Documented descriptors: 80
  • Public reference pages: 80
  • Source repository: https://github.com/MADPANDA3D/QDRANT-MCP
  • Catalog version: qdrant-2026.07.12.2
  • Catalog verified: 2026-07-12T20:51:15.5623+00:00 (5 days old)
  • Guide verified: not manually verified (not verified)
  • Committed snapshot: catalog-5ec40de147b11c40
  • Docs generated: 2026-07-18T00:19:58.776Z

Read-only Tools​

  • Get Ingest Status — Get status, stage, and diagnostics for an async textbook ingest job.
  • List Collections — Return collections currently available for the configured cluster.
  • Qdrant Audit Memories — Use this when you need to audit stored memories for missing fields, invalid payloads, and duplicates. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Build Context — Use this when you need to build a cited, token-budgeted context pack from relevant vector-memory matches. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Check Configuration — Use this when you need to check Portal, Qdrant, embedding, cache, and upload readiness without returning credential values. It does not intentionally change Qdrant or MCP state. It reads the provider-owned catalog in memory and does not contact Qdrant. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Check Configuration — Use this when you need to check Portal, Qdrant, embedding, cache, and upload readiness without returning credential values. It does not intentionally change Qdrant or MCP state. It reads the provider-owned catalog in memory and does not contact Qdrant. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema. Prefer its typed replacement when one is available because this tool remains in the legacy tier.
  • Qdrant Collection Aliases — Use this when you need to list aliases that resolve to one collection. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Collection Cluster Info — Use this when you need to inspect shard and cluster placement for one collection. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Collection Exists — Use this when you need to check whether one named Qdrant collection exists. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Collection Info — Use this when you need to retrieve a collection's configuration, vectors, and payload schema. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Collection Payload Schema — Use this when you need to list a collection's payload schema and indexed fields. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Collection Stats — Use this when you need to retrieve collection point, segment, and status statistics. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Collection Vectors — Use this when you need to list a collection's vector names, dimensions, and distance settings. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Count Points — Use this when you need to count points matching an optional structured memory filter. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Describe Collection — Use this when you need to summarize one collection's size, vectors, indexes, and useful retrieval paths. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Find Near Duplicates — Use this when you need to find semantic near-duplicate point groups without changing them. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Find Short Term — Use this when you need to search the configured short-term memory collection. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Find Tools — Use this when you need to find Qdrant tools for a multi-word task using deterministic local catalog search. It does not intentionally change Qdrant or MCP state. It reads the provider-owned catalog in memory and does not contact Qdrant. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Find Tools — Use this when you need to find Qdrant tools for a multi-word task using deterministic local catalog search. It does not intentionally change Qdrant or MCP state. It reads the provider-owned catalog in memory and does not contact Qdrant. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema. Prefer its typed replacement when one is available because this tool remains in the legacy tier.
  • Qdrant Get Endpoint Coverage — Use this when you need to review covered Qdrant API areas and intentionally excluded provider operations. It does not intentionally change Qdrant or MCP state. It reads the provider-owned catalog in memory and does not contact Qdrant. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Get Endpoint Coverage — Use this when you need to review covered Qdrant API areas and intentionally excluded provider operations. It does not intentionally change Qdrant or MCP state. It reads the provider-owned catalog in memory and does not contact Qdrant. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema. Prefer its typed replacement when one is available because this tool remains in the legacy tier.
  • Qdrant Get Points — Use this when you need to retrieve known Qdrant points by stable identifier. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Get Tool Usage — Use this when you need to retrieve one complete tool descriptor by native name, canonical name, or compatibility alias. It does not intentionally change Qdrant or MCP state. It reads the provider-owned catalog in memory and does not contact Qdrant. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Get Tool Usage — Use this when you need to retrieve one complete tool descriptor by native name, canonical name, or compatibility alias. It does not intentionally change Qdrant or MCP state. It reads the provider-owned catalog in memory and does not contact Qdrant. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema. Prefer its typed replacement when one is available because this tool remains in the legacy tier.
  • Qdrant Get Vector Name — Use this when you need to resolve the active vector name used by this MCP. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Health Check — Use this when you need to verify Qdrant collection, index, embedding, and configuration health. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Job Logs — Use this when you need to read a bounded tail of safe maintenance-job logs. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Job Progress — Use this when you need to read progress counters and phase for a maintenance job. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Job Result — Use this when you need to retrieve the final result of a completed maintenance job. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Job Status — Use this when you need to read the current state and safe summary of a maintenance job. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant List Aliases — Use this when you need to list all collection aliases visible to the configured account. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant List Capabilities — Use this when you need to inspect capability groups, catalog counts, and optionally the complete lossless ToolManifest. It does not intentionally change Qdrant or MCP state. It reads the provider-owned catalog in memory and does not contact Qdrant. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant List Capabilities — Use this when you need to inspect capability groups, catalog counts, and optionally the complete lossless ToolManifest. It does not intentionally change Qdrant or MCP state. It reads the provider-owned catalog in memory and does not contact Qdrant. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema. Prefer its typed replacement when one is available because this tool remains in the legacy tier.
  • Qdrant List Full Snapshots — Use this when you need to list full-storage snapshots on the configured Qdrant server. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant List Points — Use this when you need to scroll point identifiers and optional payloads with bounded pagination. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant List Shard Snapshots — Use this when you need to list snapshots for one collection shard. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant List Snapshots — Use this when you need to list snapshots for one collection. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Metrics Snapshot — Use this when you need to capture bounded collection and index health metrics. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Optimizer Status — Use this when you need to inspect optimizer configuration and index coverage for a collection. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Recommend Memories — Use this when you need to retrieve memories related to positive examples while excluding negative examples. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Study Search — Use this when you need to search study material with compact results and exact academic metadata filters. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Suggest Filters — Use this when you need to sample indexed metadata values and suggest exact retrieval filters. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Summarize Collection Schema — Use this when you need to map indexed payload schema to supported memory-filter fields. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Validate Memory — Use this when you need to validate a proposed memory contract and receive governance recommendations before ingest. It does not intentionally change Qdrant or MCP state. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Semantic Search — Run similarity search with optional metadata filters.

Write and Destructive Tools​

  • Cancel Ingest Job — Request cancellation for a running textbook ingest job.
  • Ingest Document — Ingest general documents/content (document workflow) from source URL or inline text.
  • Ingest Textbook (Async) — Submit a source_url textbook ingestion job and return immediately with job_id.
  • Qdrant Append File Upload — Use this when you need to append one ordered base64 chunk to an active bounded upload session. It creates or extends Qdrant or MCP-managed state without deleting existing provider data by default. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Backfill Memory Contract — Use this when you need to preview or fill missing memory-contract and governance fields. It creates or extends Qdrant or MCP-managed state without deleting existing provider data by default. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Bulk Patch — Use this when you need to overwrite payload fields on a bounded point set selected by IDs or filter. It can overwrite, remove, cancel, restore, or otherwise irreversibly change state and therefore requires the manifest-defined Portal confirmation. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Cache Memory — Use this when you need to store one short-term memory with a bounded expiry. It creates or extends Qdrant or MCP-managed state without deleting existing provider data by default. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Cancel Job — Use this when you need to stop a running maintenance job. It can overwrite, remove, cancel, restore, or otherwise irreversibly change state and therefore requires the manifest-defined Portal confirmation. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Create Collection — Use this when you need to create a collection using the active embedding vector contract and default indexes. It creates or extends Qdrant or MCP-managed state without deleting existing provider data by default. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Create Snapshot — Use this when you need to create a new point-in-time collection snapshot. It creates or extends Qdrant or MCP-managed state without deleting existing provider data by default. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Dedupe Memories — Use this when you need to find exact duplicate memories and optionally remove redundant points. It can overwrite, remove, cancel, restore, or otherwise irreversibly change state and therefore requires the manifest-defined Portal confirmation. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Delete By Filter — Use this when you need to permanently delete every point matching a bounded filter. It can overwrite, remove, cancel, restore, or otherwise irreversibly change state and therefore requires the manifest-defined Portal confirmation. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Delete Document — Use this when you need to permanently delete all chunks belonging to one document identifier. It can overwrite, remove, cancel, restore, or otherwise irreversibly change state and therefore requires the manifest-defined Portal confirmation. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Delete Points — Use this when you need to permanently delete selected points by identifier. It can overwrite, remove, cancel, restore, or otherwise irreversibly change state and therefore requires the manifest-defined Portal confirmation. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Ensure Payload Indexes — Use this when you need to create missing payload indexes required by the maintained memory contract. It creates or extends Qdrant or MCP-managed state without deleting existing provider data by default. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Expire Memories — Use this when you need to archive or delete memories whose expiry timestamp has passed. It can overwrite, remove, cancel, restore, or otherwise irreversibly change state and therefore requires the manifest-defined Portal confirmation. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Expire Short Term — Use this when you need to delete expired points from the short-term memory collection. It can overwrite, remove, cancel, restore, or otherwise irreversibly change state and therefore requires the manifest-defined Portal confirmation. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Finish File Upload — Use this when you need to finalize an upload and return upload URI aliases for a later ingest call. It creates or extends Qdrant or MCP-managed state without deleting existing provider data by default. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Ingest Class Manifest — Use this when you need to run the legacy class-manifest alias for the typed school-manifest ingest workflow. It creates or extends Qdrant or MCP-managed state without deleting existing provider data by default. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema. Prefer its typed replacement when one is available because this tool remains in the legacy tier.
  • Qdrant Ingest Manifest — Use this when you need to run the legacy generic alias for the typed school-manifest ingest workflow. It creates or extends Qdrant or MCP-managed state without deleting existing provider data by default. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema. Prefer its typed replacement when one is available because this tool remains in the legacy tier.
  • Qdrant Ingest School Manifest — Use this when you need to ingest a batch of school capture items with shared metadata and search-back verification. It creates or extends Qdrant or MCP-managed state without deleting existing provider data by default. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Ingest With Validation — Use this when you need to validate, govern, optionally quarantine, and store one memory. It creates or extends Qdrant or MCP-managed state without deleting existing provider data by default. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Link Memories — Use this when you need to replace or extend related-memory links and associations. It can overwrite, remove, cancel, restore, or otherwise irreversibly change state and therefore requires the manifest-defined Portal confirmation. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Merge Duplicates — Use this when you need to merge duplicate points into one canonical record and remove redundant records. It can overwrite, remove, cancel, restore, or otherwise irreversibly change state and therefore requires the manifest-defined Portal confirmation. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Migrate Collection Embedding — Use this when you need to add and populate the active named vector on a legacy collection. It creates or extends Qdrant or MCP-managed state without deleting existing provider data by default. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Patch Payload — Use this when you need to overwrite selected payload metadata fields on a known point. It can overwrite, remove, cancel, restore, or otherwise irreversibly change state and therefore requires the manifest-defined Portal confirmation. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Promote Short Term — Use this when you need to copy selected short-term memories into a long-term collection and optionally remove their source records. It can overwrite, remove, cancel, restore, or otherwise irreversibly change state and therefore requires the manifest-defined Portal confirmation. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Reembed Points — Use this when you need to overwrite selected vectors with embeddings from the active model. It can overwrite, remove, cancel, restore, or otherwise irreversibly change state and therefore requires the manifest-defined Portal confirmation. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Restore Snapshot — Use this when you need to restore collection state from a snapshot or approved snapshot URL. It can overwrite, remove, cancel, restore, or otherwise irreversibly change state and therefore requires the manifest-defined Portal confirmation. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Start File Upload — Use this when you need to start a bounded temporary upload session for caller-local document bytes. It creates or extends Qdrant or MCP-managed state without deleting existing provider data by default. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Submit Job — Use this when you need to submit a legacy generic maintenance job when no typed direct workflow is suitable. It can overwrite, remove, cancel, restore, or otherwise irreversibly change state and therefore requires the manifest-defined Portal confirmation. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema. Prefer its typed replacement when one is available because this tool remains in the legacy tier.
  • Qdrant Tag Memories — Use this when you need to append or replace labels on selected memories. It can overwrite, remove, cancel, restore, or otherwise irreversibly change state and therefore requires the manifest-defined Portal confirmation. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Update Optimizer Config — Use this when you need to overwrite bounded optimizer settings for one collection. It can overwrite, remove, cancel, restore, or otherwise irreversibly change state and therefore requires the manifest-defined Portal confirmation. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Qdrant Update Point — Use this when you need to replace a point's content and metadata while recomputing its embedding. It can overwrite, remove, cancel, restore, or otherwise irreversibly change state and therefore requires the manifest-defined Portal confirmation. It contacts the configured Qdrant service or uses MCP-owned job/upload state. Returns normalized provider data in data plus safe request and trace metadata in meta. Requires an authenticated MAD MCP Portal request and any provider configuration named by the input schema.
  • Store Vectorized Text — Chunk and store text with metadata in a target collection.