原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Lsp MCP

作者:theUpsider版本 0.1.6i★ –i在你的电脑上运行
注册名称io.github.theUpsider/lsp-mcp

安装

概览

作者提供的说明(英文原文)

Universal LSP MCP server

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 其他

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 注册中心没有列出需要填写的密钥。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "lsp": {
      "command": "npx",
      "args": [
        "-y",
        "@theupsider/lsp-mcp"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add lsp -- npx -y @theupsider/lsp-mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "lsp": {
      "command": "npx",
      "args": [
        "-y",
        "@theupsider/lsp-mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "lsp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@theupsider/lsp-mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 theUpsider 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 18639 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 18639 个服务器的 7% 更新
  • 基础检查结果等于或优于此分类中其他 18639 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Lsp MCP 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.1.6)于6个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, Statuser

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

作者:formulahendry起步阶段↓ 66/周★ 44014个月前更新

在你的电脑上运行

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

作者:desktop-commander正在增长★ 2113天前更新

在云端运行✓ desktopcommander.app

Statuser

Monitor services, manage incidents and status pages in Statuser.cloud from your AI assistant.

作者:statuser-cloud起步阶段↓ 1033/周今天更新

电脑或云端

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Universal LSP MCP Server

One MCP server to rule all Language Servers — automatic language detection, zero-config setup.

Overview

A Model Context Protocol (MCP) server that gives language models access to Language Server Protocol (LSP) functionality across all major programming languages. Unlike existing LSP-MCP servers, this project supports 13 languages out of the box with zero manual configuration — it automatically detects your codebase, selects the right language server, and exposes all LSP operations through a stable, language-independent tool interface.

Supported Languages

LanguageLanguage ServerAuto-Detected Via
Pythonpyright / pylsppyproject.toml, setup.py
TypeScripttypescript-language-servertsconfig.json
JavaScripttypescript-language-serverpackage.json
C#omnisharp*.csproj, *.sln
Javavscode-java / jdtlspom.xml, build.gradle
Gogoplsgo.mod
Rustrust-analyzerCargo.toml
C / C++clangd*.c, *.cpp, *.h
RubysolargraphGemfile
PHPintelephensecomposer.json
Kotlinkotlin-language-serverbuild.gradle.kts
Swiftsourcekit-lspPackage.swift

Features

  • 🔍 Automatic Language Detection — Scans project root for language markers (package.json, Cargo.toml, go.mod, etc.)
  • 🔄 Auto Language Server Selection — Hardcoded mapping with fallback servers; installs missing LSPs automatically
  • 🤖 Hands-Free Initialization — Clients that support MCP Roots auto-initialize on connect — lsp_init disappears from the tool list once all servers start cleanly
  • 💾 Cross-Session Persistence — Initialized workspaces and their ready languages are remembered across server restarts
  • 🔁 Graceful Degradation — lsp_init reappears if a previously-working server starts failing (e.g. language added, binary missing)
  • 🛠 12 LSP Tools — Definition, references, symbols, diagnostics, rename, code actions, formatting, and more
  • 📝 Read & Write Operations — Both inspection and modification of code via LSP
  • 🌐 Polyglot Support — Multiple language servers run simultaneously in the same project
  • 📋 Hybrid Responses — Human-readable text field + raw LSP data in raw field
  • 🔌 MCP Stdio Protocol — Works with any MCP-compatible client
  • ⚡ Zero Config — Install and run, no per-language setup required

Installation

Important: Install lsp-mcp on the same machine where your code lives. The language servers it manages need direct filesystem access to your codebase — they cannot work over a remote connection or on a different machine than your source files.

# npm

npm install -g @theupsider/lsp-mcp@latest

bun

bun install -g @theupsider/lsp-mcp@latest

Quickstart

VS Code / Cursor

Add to your workspace .vscode/mcp.json (recommended — ensures the server runs on the same machine as your code, including SSH remotes, WSL, and Dev Containers):

{

"servers": { "lsp-mcp": { "type": "stdio", "command": "npx", "args": ["-y", "@theupsider/lsp-mcp@latest"] } } }

Why workspace config? VS Code runs servers defined in .vscode/mcp.json wherever the workspace lives. Servers defined in your user profile always run locally — which breaks LSP when your code is on a remote machine.

CLI
# Run the server (reads from stdin, writes to stdout)

lsp-mcp

The server starts with no active project. Most clients auto-initialize when they support the MCP Roots protocol (VS Code, Copilot, etc.), but lsp_init remains available as a manual override.

For clients without Roots support, the first action the model must take is calling lsp_init:

lsp_init({ root: "/path/to/your/project" })

lsp_init will:

  1. Scan the root for language markers and start matching language servers (best-effort)
  2. Disappear from the tool list when you called it explicitly — subsequent calls to any LSP tool trigger lazy server startup for that file's language if no server was detected at init time
  3. Return health status for all servers that were started eagerly

Optional: pre-warm specific languages (skips detection, faster cold start):

lsp_init({ root: "/path/to/project", languages: ["python", "typescript"] })

Persistence: Once initialized, the workspace configuration (detected languages) is saved to your OS-standard config directory (~/.config/lsp-mcp/ on Linux, ~/Library/Application Support/lsp-mcp/ on macOS, %APPDATA%\lsp-mcp\ on Windows). On subsequent server startups, the MCP server will automatically reconnect using the last-known root, so you rarely need to call lsp_init again.

Re-emergence: If a language server that was previously healthy fails to start (e.g. you added a new language or removed a binary), lsp_init will reappear in the tool list, signaling the model should re-initialize.

Available Tools

Read-Only Tools
ToolDescriptionKey ParametersVisibility
lsp_initInitialize server for a project rootroot (required), languages (optional string array)Conditional — hidden after a successful explicit lsp_init call
lsp_definitionGo to definitionfile, line, characterAlways
lsp_referencesFind all referencesfile, line, characterAlways
lsp_document_symbolsList symbols in a filefileAlways
lsp_workspace_symbolsSearch symbols across workspacequery (limit: 100–500 results)Always
lsp_diagnosticsGet errors & warningsfile (scope: file or workspace)Always
lsp_type_definitionGo to type definitionfile, line, characterAlways
lsp_implementationFind implementationsfile, line, characterAlways
lsp_healthCheck status of all LSP servers_(none)_Always
Write Tools
ToolDescriptionKey Parameters
lsp_renameRename symbolfile, line, character, newName
lsp_code_actionApply / list code actionsfile, line, character, apply
lsp_formattingFormat documentfile
lsp_range_formattingFormat code rangefile, range

Configuration

Environment VariableDescriptionDefault
LSP_MCP_LOG_LEVELLog level: error, info, debuginfo

Setup Scripts

Two helper scripts are included for setting up a development environment:

  • `setup-languages-ubuntu24.sh` — Installs all language runtimes, compilers, and toolchains on Ubuntu 24.04 (Python, Node.js, Java, Go, Rust, Ruby, PHP, Kotlin, Swift, etc.)
  • `setup-lsp.sh` — Installs all language servers (pyright, typescript-language-server, omnisharp, jdtls, gopls, rust-analyzer, clangd, solargraph, intelephense, kotlin-language-server)
# 1. Install language runtimes

chmod +x setup-languages-ubuntu24.sh ./setup-languages-ubuntu24.sh

2. Install language servers

chmod +x setup-lsp.sh ./setup-lsp.sh

3. Reload PATH

source ~/.bashrc

Troubleshooting

Language server not found

If a language server cannot be auto-installed, the server logs a structured error and continues running for other languages. Manually install the missing server:

# Python

pipx install python-lsp-server

C

dotnet tool install -g omnisharp-roslyn

Java

npm install -g vscode-java

Ruby

gem install solargraph

Server not detecting language

Ensure your project root contains a language marker file (e.g., package.json for TypeScript, Cargo.toml for Rust). The server scans the directory passed to lsp_init for these markers.

High memory usage

Each language server runs as a separate process. For large projects with many languages, consider limiting the workspace or using LSP_MCP_LOG_LEVEL=info to monitor server health.

Architecture

┌─────────────────────────────────────────────┐

│ MCP Client (AI Model) │ └──────────────────┬──────────────────────────┘ │ MCP Protocol (stdio) ▼ ┌─────────────────────────────────────────────┐ │ LSP MCP Server (Node.js) │ │ ┌───────────┐ ┌──────────┐ ┌───────────┐ │ │ │ lsp_init │ │ lsp_... │ │ lsp_... │ │ │ └─────┬─────┘ └────┬─────┘ └─────┬─────┘ │ │ └─────────────┼─────────────┘ │ │ ▼ │ │ Language Router & Adapter │ │ (auto-detects language → selects LSP) │ └──────┬──────────┬──────────┬───────────┬─────┘ │ │ │ │ ▼ ▼ ▼ ▼ pyright typescript gopls clangd pylsp lsp rust- ... analyzer

License

Apache-2.0

问 PopNx