[CALYPSO LIST KNOWLEDGE BUCKETS] Lists knowledge buckets for the team tied to the configured Calypso API key.

Use this before uploads when you need bucket ids, slugs, names, member counts, or bucket-store readiness. This complements RAG model discovery: model discovery shows which buckets are bound to each agent variant, while this tool lists all buckets for the API key team.

[CALYPSO UPLOAD KNOWLEDGE FILE] Uploads a file into the durable bucket-backed knowledge store and indexing pipeline.

Use this when you want a file indexed into the broader knowledge corpus instead of attached directly to a single RAG chat turn. This tool returns knowledge-file and task metadata. A bucket destination is required: pass bucketIds, bucketSlugs, or bucket. Choose exactly one file source. Use filePath when this MCP server runs locally and can read the path, including Claude Desktop or Cursor configs that launch this package with npx. Use contentBase64 for hosted or remote MCP clients, browser uploads, generated in-memory content, or remote sandbox files that this MCP process cannot read. Do not base64-encode local files just to use this tool.

[CALYPSO UPLOAD KNOWLEDGE FILES BATCH] Uploads 1 to 100 files into the durable knowledge store and indexing queue in one request.

Use this for bulk corpus ingestion. Shared bucket fields apply to every item unless an item provides its own bucket fields. The tool returns batch-level status and, when requested, polls until the batch reaches active, partially_active, partially_failed, failed, or timeout. A shared bucket destination is required unless every item provides its own bucket destination. Choose exactly one file source per item. Use filePath when this MCP server runs locally and can read each path, including Claude Desktop or Cursor configs that launch this package with npx. Use contentBase64 for hosted or remote MCP clients, browser uploads, generated in-memory content, or remote sandbox files that this MCP process cannot read. Do not base64-encode local files just to use this tool.

[CALYPSO RAG AGENT] Sends each prompt directly to the Calypso RAG agent using the full conversation context.

Use this when you want Calypso knowledge retrieval and grounded answers from the RAG backend. Typical requests:

• "Summarize the key points from our onboarding documentation"

• "What does the knowledge base say about campaign approval rules?"

• "Compare the documented indexing flow with the retrieval flow"

• "Answer using the uploaded file ids: ["file_123"]"

Responses API behavior:

• First turns start a named Calypso conversation via /v1/responses.

• Follow-up turns chain with previous_response_id so the backend owns conversation state.

• When fileIds are provided, the MCP uses rag_policy retrieval semantics instead of inline attachment stuffing.

MCP session behavior:

• This tool maintains a stable conversation id in the background for multi-turn retrieval context.

• Use /new to start a fresh conversation and clear the current context window.

Quick commands (examples):

• "Summarize the latest indexed knowledge about WhatsApp templates"

• "Find the source of truth for campaign approval behavior"

• "Start a new topic" (or use /new)

Available RAG models: calypso-rag-agent.