Qdrant Cloud

Operate Qdrant Cloud through your OOMOL-connected account. This skill calls the qdrant connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Qdrant Cloud. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "qdrant" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "qdrant" --action "<action_name>" --data '<json>' --json

• --data takes a JSON object string or @path/to/file.json; omit it to send {}.
• The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

• create_collection — Create a Qdrant Cloud collection with one unnamed dense vector configuration. [write]
• get_collection — Retrieve configuration and status information for one Qdrant collection.
• get_point — Retrieve one point by numeric ID or UUID from a Qdrant collection.
• list_collections — List the Qdrant collections visible to the authenticated API key.
• query_points — Search a dense-vector Qdrant collection with an optional payload filter.
• scroll_points — Read one page of points from a Qdrant collection with an optional payload filter.
• upsert_points — Insert or replace dense-vector points in a Qdrant collection and wait for the write to commit. [destructive]

Safety

• Untagged actions are reads (get / list / search) — safe to run directly.
• Actions tagged [write] change Qdrant Cloud state — confirm the exact payload and effect with the user before running.
• Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

• oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  

  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
  

• Not signed in / authentication error — sign in to your OOMOL account once:

  oo auth login
  

• scope_missing / credential_expired / app_not_ready / app_not_found — Qdrant Cloud is not connected, or the connection expired or lacks a scope. Connect once (auth type: custom credential) at:

  https://console.oomol.com/app-connections?provider=qdrant
  

• HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

• Qdrant Cloud homepage: https://qdrant.tech/cloud/