claude-context: "Error validating collection creation: [object Object]" when indexing codebase
I'm using the claude-context MCP server (zilliztech/claude-context) to index a large codebase on macOS (Apple Silicon) with Node.js v22.12.0. Every call to
mcp__code-context__index_codebasefails during collection creation withError validating collection creation: [object Object], regardless of splitter type (ast/langchain),force: true, or path format. How can I get more detailed error information or work around this?Originally asked on GitHub: https://github.com/zilliztech/claude-context/issues/126
6 answers
The issue is still open as of August 2025, but a maintainer replied with debugging steps and a suspected cause.
The maintainer suspects the
Error validating collection creation: [object Object]error is caused by hitting the limit on the number of collections on Zilliz Cloud. PR #130 makes this error explicitly returned as part of the MCP response so the AI agent can identify the problem. The reporter separately noted that the[object Object]text suggests the error object isn't being serialized/displayed properly, which makes debugging harder.Steps from the thread:
- Start your CLI with the debug flag to see detailed logs:
claude --debug, orqwen --debug. - Upgrade to the latest release. The project and npm package were renamed to Claude Context; the latest released version is 0.1.0, published as
@zilliz/claude-context-mcpon npm. Try it to see if it resolves the problem. - If you hit
create duplicate collection with different parametersinstead, prompt the agent with "clear the index of this codebase" and then reindex.
Another user reported the same error after a
search_codequery; their debug log showed the codebase tracked as "not marked as indexed" and the search returnedCodebase ... is not indexed. Please index it first using the index_codebase tool.A maintainer responding noted the model should automatically identify the codebase path rather than passing a placeholder; if the model keeps generating poor tool parameters, consider using a better model or a different MCP client.Did this work for you?- Start your CLI with the debug flag to see detailed logs:
What a GitHub user tried on GitHub (Didn't work)
Reporter cleared the existing index with
clear_index, tried bothastandlangchainsplitters, usedforce: true, custom extensions, and absolute paths. The error reproduced 100% of the time across all combinations.Source: https://github.com/zilliztech/claude-context/issues/126 (opens external site)
Did this work for you?What @zc277584121 tried on GitHub (Outcome unclear)
Maintainer suggested starting the CLI with
--debug(e.g.,claude --debug) to get detailed logs, and suspected the Zilliz Cloud collection limit as the cause.Did this work for you?What @zc277584121 tried on GitHub (Outcome unclear)
Maintainer noted the project was renamed to Claude Context and pointed to the latest release 0.1.0, published on npm as
@zilliz/claude-context-mcp.Did this work for you?What @zc277584121 tried on GitHub (Outcome unclear)
Maintainer suggested fixing
create duplicate collection with different parametersby asking the agent to "clear the index of this codebase" and then reindexing.Did this work for you?What @qualified5083 tried on GitHub (Outcome unclear)
Another user reported the same error occurring after a
search_codequery. Their debug log showed the codebase path tracked as "not marked as indexed" and the search returned the "not indexed" message. No fix was attempted in the thread.Did this work for you?
Related questions
- 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)?
- claude-context search_code: 'codebase is not indexed' after successful indexing?