Ext Ops Panel
Open dashboard
Comparison

golang vs LSP-MCP Bridge

golang is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.

golang is a plugin bundle for AI coding tools published by cblecker. No marketplace we read lists it any more. LSP-MCP Bridge is an MCP server published by Stryk91. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplacegolangLSP-MCP Bridge
Community marketplace cblecker/claude-plugins Removed on 2026-10-20
Version: 1.0.0
Forks (GitHub): 4
Stars (GitHub): 5
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

golang vs LSP-MCP Bridge
Factgolangno longer listed · LSP-MCP Bridge
Marketplaces that list it (differs)01
Stars (GitHub) (differs)51
Forks (GitHub) (differs)40
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (https://github.com/Stryk91/lsp-mcp-rs/releases/download/v0.1.0/lsp-mcp-rs.exe)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)3Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/cblecker/claude-pluginsgithub.com/stryk91/lsp-mcp-rs
Changes in the last 7 days (differs)20
First seen (differs)2026-10-152026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of golang

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • gopls-lsp

    Go language server for code intelligence and refactoring

    by Anthropic · Plugin bundle

    Listed on: Claude Code: claude-plugins-official · Describes nearly the same job

  • gopls-mcp

    Semantic Go code analysis using gopls — type-aware definitions, references, implementations, and call hierarchy.

    by xieyuschen · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • go-dev

    Go-specific development tools with best practices

    by Gopher Guides · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • gopls-mcp io.github.xieyuschen/gopls-mcp

    Semantic code analysis for Go using gopls - language-aware navigation, definitions, references

    by xieyuschen · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • lspmesh

    LSP aggregator + MCP server - fronts TypeScript, Tailwind, and Biome behind one LSP endpoint, with by-name symbol/reference/implementation search.

    by Filiph Sandström · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes a similar job

  • go

    Go language coding standards, best practices, and testing patterns

    by Ben Drucker · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes a similar job

Its card, with similar plugins by marketplace

What each says it does

golang

In its own words, on Community GitHub marketplaces:

Go development tools: gopls MCP and LSP servers, plus automatic gofmt formatting of edited Go files

LSP-MCP Bridge

In its own words, on Official MCP Registry:

Universal MCP bridge to LSP servers. One binary, 6 languages, config-driven.

How to run each

golang

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

LSP-MCP Bridge

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: golang · What it can do: LSP-MCP Bridge · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built