Marketplace for trusted AI agent skills

Skill Detail

Give MCP clients language-server code intelligence

Expose LSP-backed definition, reference, rename, and diagnostic tools to MCP clients so coding agents can inspect code semantics before editing.

Developer ToolsMCP
Developer Tools MCP Security Reviewed
⭐ 1.5k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill give-mcp-clients-language-server-code-intelligence Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
View source
At a glance
Tools required
MCP-capable client, Go toolchain, and a language server for the target programming language
Install & setup
Install the MCP server with go install github.com/isaacphi/mcp-language-server@latest, install the language server required for the target codebase, then configure the MCP client to launch mcp-language-server with the appropriate language-server command.
Author
isaacphi
Publisher
Individual
Last updated
Jun 5, 2026
Quick brief

Use MCP Language Server when an MCP-capable coding agent needs semantic code navigation instead of plain text search. The operator installs the MCP server, installs the relevant language server for the target codebase, adds the server to the MCP client config, and then lets the agent call tools such as definition, references, rename, and diagnostics during review or implementation. Invoke this instead of using an editor manually when the agent needs repeatable language-server context inside its own tool loop. The scope boundary is narrow: expose existing language-server capabilities through MCP for code intelligence, not a generic IDE, LSP framework, or broad developer-tools listing.

How it works

What this skill actually does

Inputs and prerequisites: MCP-capable client, Go toolchain, and a language server for the target programming language.

Setup notes: Install the MCP server with `go install github.com/isaacphi/mcp-language-server@latest`, install the language server required for the target codebase, then configure the MCP client to launch `mcp-language-server` with the appropriate language-server command.

Source and verification boundary: use https://github.com/isaacphi/mcp-language-server as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a MCP workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.