Agent Lsp
Give your agent language-server powers—definitions, refs, and diagnostics—across 30+ languages through a stateful LSP MCP runtime.
Overview
Agent LSP is an MCP server for the Build phase that exposes a stateful LSP runtime with 50+ tools across 30+ languages to coding agents.
What is this MCP server?
- Stateful LSP runtime designed for long agent sessions
- 50+ MCP tools mapped from language-server capabilities
- 30+ programming languages supported
- npm package @blackwell-systems/agent-lsp with stdio transport
- Version 0.9.0 on GitHub blackwell-systems/agent-lsp
- 30+ languages
- Package version 0.9.0
Community signal: 52 GitHub stars.
What problem does it solve?
Agents without LSP see files as text and miss reliable go-to-definition, references, and language-aware refactors across your real stack.
Who is it for?
Solo builders running local MCP who ship polyglot code and want agent sessions that behave more like an IDE attached to the repo.
Skip if: Builders who only touch one small script language with no LSP server installed, or who refuse local Node/npm MCP processes.
What do I get? / Deliverables
Your agent calls LSP-backed MCP tools so multi-file edits and debugging stay aligned with how your languages actually compile and resolve symbols.
- 50+ LSP-derived tools available to the agent over MCP
- Stateful analysis session across edits in 30+ languages
Recommended MCP Servers
Journey fit
Build is where you wire agent ergonomics; LSP-backed tooling directly improves how agents edit and reason about codebases during implementation. Agent-tooling is the right shelf because this server is infrastructure for coding agents, not a standalone app feature.
How it compares
Local LSP-backed MCP runtime, not a cloud code-search index or a prompt-only refactor skill.
Common Questions / FAQ
Who is Agent LSP for?
Developers using Claude Code, Cursor, or Codex who want MCP tools backed by real language servers across many languages in one agent workflow.
When should I use Agent LSP?
During Build when you are implementing features, refactoring, or fixing type and symbol errors and need the agent to use LSP operations instead of blind search.
How do I add Agent LSP to my agent?
Install @blackwell-systems/agent-lsp from npm, add an MCP server entry with stdio transport pointing at the package binary, and ensure relevant language servers are installed locally.