Ext Ops Panel
Open dashboard
Comparison

php-lsp-claude-code-plugin vs LSP-MCP Bridge

php-lsp-claude-code-plugin is a plugin bundle for AI coding tools published by jorgsowa. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacephp-lsp-claude-code-pluginLSP-MCP Bridge
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 4
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

php-lsp-claude-code-plugin vs LSP-MCP Bridge
Factphp-lsp-claude-code-pluginLSP-MCP Bridge
Marketplaces that list it11
Stars (GitHub) (differs)4 (better)1 (worse)
Forks (GitHub)00
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
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/jorgsowa/claude-php-lsp-plugingithub.com/stryk91/lsp-mcp-rs
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

php-lsp-claude-code-plugin

In its own words, on Claude Code: claude-plugins-community:

A Claude Code LSP plugin that wires up php-lsp — a full-featured PHP language server written in Rust, much faster than any of existing implementation

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

php-lsp-claude-code-plugin As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install php-lsp-claude-code-plugin@claude-community

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: php-lsp-claude-code-plugin · What it can do: LSP-MCP Bridge · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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