gortex vs serena
Code-intelligence engine in one static Go binary: tree-sitter graph over 257 languages, compiler-grade resolution for 17, multi-repo, 175 configurable MCP tools — up to 50x fewer tokens. 100% local. — 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.
Both give agents symbol-level code intelligence over MCP. Gortex ships one static Go binary with a tree-sitter graph across 257 languages and compiler-grade resolution for 17; Serena leans on real language servers, so its depth follows the LSP ecosystem rather than its own parsers.
| gortex | serena | |
|---|---|---|
| Stars | 1.3k | 28k |
| Forks | 122 | 1.9k |
| Language | Go | Python |
| License | Apache-2.0 | MIT |
| Last activity | 4 days ago | 4 days ago |
| Topics | code-intel, local | code-intel, coding |
| Curated connections | 5 | 4 |
gortex — the curator's take
The coverage play on this shelf: 257 grammars, cross-repo and cross-SERVICE edges (HTTP routes, contracts) with a provenance/confidence tier the single-repo tools don't attempt, and one install that configures 19 coding agents. When NOT: 175 MCP tools is a context bill of its own — prune the toolset or your agent pays the index's price in schema tokens; benchmarks are self-published; and if you want memory as plain files, this is the opposite philosophy.
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.