Comment by CharlesW

2 days ago

It's strangely difficult to find official information about this, but here's what I've learned:

• Use `/plugin` to open Claude Code's plug-in manager

• In the Discover tab, enter `lsp` in the search box

• Use `spacebar` to enable the ones you want, then `i` to install

Hope that helps!

Yeah, I posted here because I was completely blindsided when my claude asked if I wanted to install a go lsp. I didnt even know that was a thing. A little googling led to this changelog from 3 days ago, but I was surprised I hadnt seen any previous mentions of this online (from either creators, anthropic, or HN posts).

I am disabling it for now since my flow is fine at the moment, I'll let others validate the usefulness first.

  • I got an unexpected offer to install the LSP plugin for swift-lsp at 6:30pm pst on 12/19pm and again yesterday afternoon the text reads:

    LSP Plugin Recommendation

    LSP provides code intelligence like go-to-definition and error checking

    Plugin: swift-lsp

    Swift language server (SourceKit-LSP) for code intelligence Triggered by: •swift files

    Would you like to install this LSP plugin? › 1. Yes, install swift-lsp 2. No, not now 3. Never for swift-lsp 4. Disable all LSP recommendations

  • I had a conversation with Claude code 2 weeks ago where it mentioned early support for LSP had been added into Claude code. Have been working on a LSP for a custom language since then.

I am on the latest version of Claude Code and nothing comes up when I follow this and search for "mcp". Looks like this feature is quite undercooked at the moment. I'm hoping for a more straightforward way to enable this and ensure the LSP is being used by Claude in the future.

Thanks! I saw typescript-lsp in the plugins list, but I wasn't sure if that was related.

That works, but even after installing the plugin, it doesn't seem to run the language server itself, so it doesn't seem to do anything in the terminal version of claude-code.

I'd be disappointed if this were a feature only for the vscode version.

Have you figured out what triggers it?