claude-context 'index codebase' fails: 'Error validating collection creation: [object Object]'
When I run
index codebasein Claude Code with the claude-context MCP server (npx @zilliz/claude-context-mcp@latest), it fails before indexing withError: Error validating collection creation: [object Object]. My config uses anOPENAI_API_KEYand aMILVUS_TOKENfor Zilliz cloud. Other users reproduced this on macOS Sequoia with Node 20.18.3 and 23.9.0 across Rust and TypeScript (NestJS) codebases — what causes it and how do I fix it?Originally asked on GitHub: https://github.com/zilliztech/claude-context/issues/215
5 answers
Still open — no fix has been released, but the thread offers a likely cause and a couple of workarounds.
Commenter 4's diagnosis (a guess, not confirmed by a maintainer): Zilliz cloud clusters allow a maximum of 5 collections per cluster. Once you reach that cap, collection creation validation fails with the generic
Error validating collection creation: [object Object]before any source file is indexed. Other users replied that this matched their situation, but the thread never shows the fix being verified.Commenter 10 later reproduced the same error and, on a subsequent attempt, got the underlying
4 DEADLINE_EXCEEDED: Deadline exceeded after 15.001sfrom the vector DB path. A later retry succeeded, so the failure can also be transient — retry once before deleting anything.Workarounds suggested in the thread (not verified there): drop a collection you no longer need in the Zilliz cluster, or run Milvus locally — commenter 7 linked the project FAQ's fully local deployment setup and guessed local Milvus may not have the same limit.
The MCP server makes this harder to debug because it collapses the thrown error object to
[object Object]instead of surfacing fields likeerror_code,reason, ordetail.General advice: your
OPENAI_API_KEYandMILVUS_TOKENare stored in plaintext in the MCP config file, so treat any copy of that file that ends up in a repository as sensitive.Did this work for you?What @PeterSenyszyn tried on GitHub (Outcome unclear)
Commenter guessed the cause: Zilliz cloud limits each cluster to 5 collections, so creating another one fails validation. Other users replied that this matched their experience, but nobody confirmed that dropping collections actually fixed it.
Did this work for you?What @dpearson2699 tried on GitHub (Partly worked)
Reproduced the same
[object Object]error, then saw4 DEADLINE_EXCEEDED: Deadline exceeded after 15.001sfrom the vector DB on a next attempt. A later retry succeeded, showing the failure can be transient.Did this work for you?What a GitHub user tried on GitHub (Didn't work)
Reporter ran the
index codebasecommand in Claude Code with the MCP config shown above (npx @zilliz/claude-context-mcp@latest); it failed during collection validation before indexing any files.Source: https://github.com/zilliztech/claude-context/issues/215 (opens external site)
Did this work for you?What @mahmoudnaif tried on GitHub (Outcome unclear)
Suggested freeing a slot by dropping one collection, or running Milvus locally following the project FAQ, noting local Milvus might not have the same limit. No confirmation in the thread.
Did this work for you?
Related questions
- claude-context: "Error validating collection creation: [object Object]" when indexing codebase
- claude-context: indexing succeeds but Milvus/Zilliz DB stays empty
- How do I stop claude-context from applying .dockerignore when indexing?
- claude-context on Windows: 'Failed to open file' path has no slashes
- Can I use claude-context without an OpenAI key (OpenRouter, Mistral, or local LM Studio)?