StackMap
Subscribe

cocoindex-code vs serena

AST-based semantic code search for coding agents: pipx install, zero config, local embeddings out of the box — a CLI/skill/MCP that cuts agent context ~70% vs grepping. Built on CocoIndex. — versus — The IDE for your coding agent: an MCP toolkit giving symbol-level retrieval, editing, refactoring and debugging over real language servers — or a JetBrains plugin backend.

The curated verdict

Retrieval by meaning versus retrieval by structure: cocoindex-code does AST-aware semantic search with local embeddings and zero config, Serena resolves actual symbols and references through the language server. Search when you don't know the name, Serena when you do.

cocoindex-codeserena
Stars2.7k28k
Forks2141.9k
LanguagePythonPython
LicenseApache-2.0MIT
Last activity17 days ago4 days ago
Topicscode-intel, localcode-intel, coding
Curated connections64

cocoindex-code — the curator's take

The lowest-friction entry in the code-context-server category: one pipx install, zero config, and the [full] variant ships local embeddings so there's no API key before first search. AST-aware chunking plus the CocoIndex engine underneath means the index stays fresh incrementally instead of rebuilding. Integrates as a skill or MCP with Claude Code, Codex, Cursor. NOT the deepest graph: it's semantic search, not call-graph analysis — no callers/blast-radius queries (that's TokenSave or codegraph-mcp territory) — and the slim install quietly requires a cloud embedding key while [full] costs ~1GB of torch.

serena — the curator's take

The default answer when an agent is flailing in a large codebase: cross-file renames, moves and reference lookups collapse from a dozen careful text edits into one atomic symbol-level call, because a real language server — not a regex — resolves the code. It bolts onto any MCP client (Claude Code, Codex, Cursor, JetBrains, Gemini CLI, Copilot CLI), and the evaluation methodology is refreshingly honest: they had agents score the tools on ~20 routine tasks and published the prompt. Two things to know: install from their Quick Start, not a plugin marketplace, because the marketplace commands are outdated and the maintainers say so; and the JetBrains backend is a paid plugin, while the free path depends on whichever LSP server your language has.