An MCP server for symbolic code search over multiple language servers.
Asteria was created as a lightweight alternative to Serena. It only borrows the idea of exposing three symbolic search tools - get_symbols_overview, find_symbol, and find_referencing_symbols - and does not try to replicate Serena's broader MCP toolkit.
MCP server for symbolic (LSP) code search
Sterne
2
Tools
—
Uptime
—
The server exposes a small, stable tool surface for agents that need to inspect code with minimal file reads.
WARNING: ⚠️ LSP servers are required.
Asteria does not install or manage LSP servers for you.
If the required language server is not found in PATH, the corresponding adapter fails on the first request.
See Language server installation for installation commands.
Project status
Server has been tested on macOS and Linux (Ubuntu).
Windows is not supported because many LSP servers work poorly on it.
Symbolic search tools
get_symbols_overview: returns a compact overview of symbols in one file, grouped by LSP symbol kind
find_symbol: finds symbols by path-like query across a workspace, file, or directory
find_referencing_symbols: finds usages of a symbol and groups them by file and logical container
No special prompts are required. In most cases, LLM will prefer symbolic searches in accordance with its own asteria prompt.
A workspace-local TypeScript installation takes precedence over this fallback. When an MCP client starts Asteria,
pass the variable through the MCP server environment. The repository .env file is only for development commands.
Homebrew installs llvm as a keg-only formula. If command -v clangd still returns nothing after installation, add $(brew --prefix llvm)/bin to your PATH.
Add each adapter under internal/adapters/lsp/servers/<server-name>/.
In most cases, the adapter should stay thin and reuse shared packages:
internal/adapters/lsp/runtimelsp - LSP process lifecycle, session reuse, and workspace isolation
internal/adapters/lsp/stdlsp - shared implementation for overview, symbol search, and reference search
internal/adapters/lsp/helpers - common document and workspace utilities
There are two supported approaches:
Standard adapter - use this when the language server follows standard LSP behavior closely enough for stdlsp
Custom adapter - use this when the server needs its own symbol or reference workflow
High-level flow:
Create the adapter package.
Implement router.ILSP and server.ILSP.
Register the adapter in internal/appinit/lsp.go.
Add unit and integration tests with fixtures in testdata/.
Run task lint, task test, and task itest.
For the full implementation rules, package layout, multi-workspace behavior, cache requirements, and testing checklist, read LSP Server Implementation Guide.
Language server resource usage
Asteria starts LSP sessions on demand and closes them after the configured idle timeout.
Active requests keep their session open through document cleanup.
TypeScript uses one semantic-capable tsserver with a configurable heap limit.
Rust and PHP adapters disable background diagnostics. The Python adapter limits diagnostics
to open files. The Go adapter disables Staticcheck and triggers diagnostics on save;
workspace loading and configuration changes can still trigger diagnostics.
Clangd and Marksman retain the indexing needed for symbol and reference search.
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Fragen
Wie installiere ich Asteria?
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Benötigt Asteria einen API-Schlüssel?
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
Welchen Transport verwendet Asteria?
Asteria läuft lokal über stdio.
Wann wurde Asteria zuletzt geprüft?
Zuletzt geprüft: 2026-10-28. MCP server for symbolic (LSP) code search