lsp-bridge

Unify type checking and reference analysis across languages via MCP-based LSP with CLI fallbacks.

Updated May 5, 2026
One-click install
npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill lsp-bridge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lsp-bridge
Source: https://github.com/shakhovskiya-create/shakhoff-claude-marketplace/tree/main/plugins/ai-scrum/skills/lsp-bridge
Command: npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill lsp-bridge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Universal LSP integration with safe fallback to CLI tools when MCPs are unavailable, enabling consistent type-checking and reference analysis across languages.

Core Features & Use Cases

  • Unified LSP-based type checking for multiple languages with automatic MCP detection.
  • Fallback to CLI tools for environments without MCPs, ensuring continued validation.
  • DoR/DoD workflow support: pre-task health checks, refactoring impact analysis, and post-change validation.

Quick Start

Run lsp-bridge to perform type checks and reference analysis using MCPs when available, or CLI fallbacks otherwise.

Frequently Asked Questions about lsp-bridge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I unify type checking across multiple programming languages?

Unifying type checking across multiple languages is achieved by integrating MCP-based LSP with CLI fallbacks. This detects available MCPs and routes diagnostics to the appropriate language server for TypeScript, Python, Go, or Java.

Can I run reference analysis if my environment lacks MCPs?

Reference analysis can still run without MCPs by using CLI fallbacks. When MCP detection fails, the system automatically routes type checking and reference analysis tasks to available CLI tools to ensure continued validation.

What is the best way to automate pre-task health checks and post-change verification?

Automating pre-task health checks and post-change verification is handled through DoR and DoD workflow support. It uses LSP-based type checking to evaluate refactoring impacts and validate code changes across supported languages.

Does LSP integration support DoR and DoD workflows?

LSP integration explicitly supports DoR and DoD workflows by providing structured diagnostics. It enables pre-task health checks to assess readiness and post-change validation to ensure code modifications meet project standards.

How do I perform type checking when MCP-based language servers are unavailable?

Type checking when MCP-based language servers are unavailable is handled via automatic CLI fallbacks. This ensures that structured diagnostics and reference analysis continue to function in environments without MCP support.

What languages are supported for LSP-based reference analysis?

LSP-based reference analysis supports TypeScript, Python, Go, Java, and other languages. It unifies type checking and reference analysis across these languages by integrating MCP-based LSP with CLI fallbacks.