Agent Lsp vs Code Index — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Agent Lsp vs Code Index
In-depth architectural comparison of the Agent Lsp and Code Index MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Agent Lsp
Databases · Local stdio
Quality: 67/100 (Great) | Auth: No auth required
Code Index
Databases · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Agent Lsp if you need specialized Databases tools running via a local process. Choose Code Index if your workspace requires Databases integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Agent Lsp when:
You need dedicated capabilities in the Databases domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: AGENT_LSP_OUTPUT_FORMAT.
Stateful MCP server over real language servers. 50 tools, 30 CI-verified languages, 20 agent workflows. Persistent sessions keep the index warm across files and projects. Speculative execution simulates edits in memory before writing to disk.
SQLite-backed hybrid (vector + FTS) code search index for Claude Code over MCP.
Activate phase enforcement for a skill workflow. Once active, tool calls are checked against the skill's phase permissions. Phases advance automatically as you call tools from later phases. Use this at the start of a skill workflow to enable safety guardrails that prevent out-of-order operations (e.g., applying edits before completing blast-radius analysis).
add_workspace_folder
Add a directory to the LSP workspace, enabling cross-repo references, definitions, and diagnostics. Useful when working across a library and its consumers — after adding the consumer repo, find_references on a library function returns call sites in both repos. Requires start_lsp to have been called first. Language servers that support multi-root workspaces (gopls, rust-analyzer, typescript-language-server) will re-index the new folder automatically.
apply_edit
Apply an edit to a file. Two modes: (1) WorkspaceEdit mode: pass workspace_edit with positional changes returned by rename_symbol or format_document; (2) Text-match mode: pass file_path + old_text + new_text to find and replace text. For full function/method body replacements, consider replace_symbol_body which resolves by symbol name instead of text matching. Always call preview_edit first to verify the edit is safe.
blast_radius
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Agent Lsp is categorized under Databases and uses a local stdio subprocess. In contrast, Code Index belongs to Databases using local stdio subprocess. Select Agent Lsp when you need capabilities focused on databases and Code Index when you require tools for databases.
Enumerate all exported symbols in the specified files, resolve their references across the workspace, and partition callers into test vs non-test. Returns affected_symbols (name, file, line), test_callers (with enclosing test function names), and non_test_callers. Use before editing a file to understand blast radius. Set include_transitive=true to surface second-order callers (callers of callers). Set scope='all' to include unexported symbols for comprehensive dead code detection.
callers
Find all incoming callers of a function or method. Shortcut for find_callers with direction='incoming'. Use before deleting or refactoring a function to see who depends on it.
close_document
Close a file in the LSP server. Use this tool when you're done with a file to free up resources and reduce memory usage. It's good practice to close files that are no longer being actively analyzed, especially in long-running sessions or when working with large codebases.
commit_session
Commit a simulation session. With apply=true, writes changes to disk and notifies LSP servers. With apply=false, returns a unified diff patch. Use after evaluate_session confirms the changes are safe.
create_simulation_session
Create a new speculative code session for simulating edits without committing to disk. Returns a session ID. Baseline diagnostics are captured lazily on first edit per file. Use this to explore what-if scenarios before applying changes.
deactivate_skill
Deactivate phase enforcement for the currently active skill. Tool calls will no longer be checked against phase permissions. Call this when the skill workflow is complete or when you need to exit the workflow early.
destroy_session
Destroy a simulation session and release all resources. Call this after commit or discard to clean up. Sessions in terminal states (committed, discarded, destroyed) cannot be reused.
detect_changes
Run git diff to identify changed files, analyze their exported symbols via blast_radius, and return affected symbols with risk classification. Risk levels: 'high' (callers from multiple packages), 'medium' (callers from same package only), 'low' (zero non-test callers). Use before committing to understand the blast radius of uncommitted or recently committed changes.
detect_lsp_servers
Scan a workspace directory for source languages and check PATH for the corresponding LSP server binaries. Returns detected workspace languages (ranked by prevalence), installed servers with their paths, and a suggested_config array ready to paste into the agent-lsp MCP server args. Use this to set up agent-lsp for a new project or verify your configuration.
+53 more tools listed on main page
Code Index Tools (14)
code_search
Hybrid (vector + FTS) search for **conceptual** queries (e.g., "auth flow", "where do we parse JSON").
symbol_lookup
Exact-name lookup of functions / classes / methods / types. Prefer over `code_search` for identifiers.
file_outline
Symbols (with signatures) in a file, in source order. Use instead of `Read` when you only need shape.
module_outline
Symbols across a directory subtree in one call. Use instead of looping `file_outline`.
where_am_i
Given `path` + `line`, returns the innermost symbol and the full enclosing chain.
get_symbol_body
Full chunk for a `symbol_id` from `symbol_lookup` / `code_search` / `file_outline`.
get_symbol_bodies
Batch version of `get_symbol_body` (up to 20 ids per call).
callers
Symbols that CALL the given symbol. `depth` (1-5) expands transitively.
callees
Symbols that the given symbol CALLS. `depth` (1-5) expands transitively.