Universal MCP bridge to LSP servers. One binary, 6 languages, config-driven.
MCP server that bridges to any LSP. One binary, multiple language servers. Create next to the binary: Add to Claude Desktop config (): Tool | Description | ------|-------------| | Get docs/type at position | | Go to definition | | Find all references | | List symbols in file | | Get errors/warnings | | List configured servers | All position arguments are 0-indexed. 1. MCP request comes in with a…
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
MCP server that bridges to any LSP. One binary, multiple language servers. Create next to the binary: Add to Claude Desktop config (): Tool | Description | ------|-------------| | Get docs/type at position | | Go to definition | | Find all references | | List symbols in file | | Get errors/warnings | | List configured servers | All position arguments are 0-indexed. 1. MCP request comes in with a file path 2. File extension maps to configured LSP server 3. LSP spawns on first use, stays running…
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.