pyright-lsp plugin: lspServers config from marketplace.json not propagated

Resolved 💬 3 comments Opened Jan 4, 2026 by AIdoux Closed Jan 7, 2026

Description

The pyright-lsp@claude-plugins-official plugin is enabled but the LSP server is not registered. The lspServers configuration defined in marketplace.json is not propagated to the installed plugin.

Steps to Reproduce

  1. Enable the pyright-lsp plugin: claude plugin install pyright-lsp
  2. Restart Claude Code
  3. Try to use LSP on a Python file:

``
LSP(operation: "documentSymbol", filePath: "app/main.py", line: 1, character: 1)
``

Expected Behavior

LSP operations should work for Python files (.py, .pyi)

Actual Behavior

No LSP server available for file type: .py

Debug Logs

2026-01-04T05:20:15.068Z [DEBUG] LSP notification handlers registered successfully for all 0 server(s)
2026-01-04T05:20:15.074Z [DEBUG] Loading plugin pyright-lsp from source: "./plugins/pyright-lsp"
2026-01-04T05:20:38.781Z [DEBUG] No LSP server available for file type .py for operation documentSymbol

Analysis

The marketplace.json correctly defines the LSP server configuration:

{
  "name": "pyright-lsp",
  "lspServers": {
    "pyright": {
      "command": "pyright-langserver",
      "args": ["--stdio"],
      "extensionToLanguage": {
        ".py": "python",
        ".pyi": "python"
      }
    }
  }
}

However, the installed plugin directory only contains a README.md file - the lspServers config is not copied/used.

Installed plugin path: ~/.claude/plugins/cache/claude-plugins-official/pyright-lsp/1.0.0/
Contents: Only README.md

Environment

  • OS: Windows 11
  • Claude Code version: Latest (Jan 2026)
  • pyright-langserver: installed and working (pyright --version returns 1.1.407)
  • Plugin enabled in ~/.claude/settings.json:

``json
{
"enabledPlugins": {
"pyright-lsp@claude-plugins-official": true
}
}
``

Workaround

None currently. Running pyright directly via Bash works, but LSP features (goToDefinition, findReferences, hover, etc.) are not available.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗