Ext Ops Panel
Open dashboard
Comparison

vbnet-lsp-claude-plugin vs CodeMap

vbnet-lsp-claude-plugin is a plugin bundle for AI coding tools published by DNAKode. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). CodeMap is an MCP server published by bbajt. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
Marketplacevbnet-lsp-claude-pluginCodeMap
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.4.0
Forks (GitHub): 6
Stars (GitHub): 21
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

vbnet-lsp-claude-plugin vs CodeMap
Factvbnet-lsp-claude-pluginCodeMap
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)21 (better)
Forks (GitHub) (differs)0 (worse)6 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (codemap-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/dnakode/vbnet-lsp-claude-plugingithub.com/bbajt/csharp-code-map
Changes in the last 7 days00
First seen (differs)2026-10-122026-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

vbnet-lsp-claude-plugin

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

vbnet-lsp adds Roslyn-powered VB.NET language intelligence to Claude Code through Language Server Protocol. It registers .vb files and launches vbnet-ls over stdio, enabling semantic diagnostics, completion, hover, definition/references navigation, and symbol-aware edits in VB.NET projects. The language server is distributed as the NuGet global tool DNAKode.VbNet.Lsp and validated in CI on Windows and Linux, including real Claude plugin validation and command checks.

CodeMap

In its own words, on Official MCP Registry:

Roslyn-powered MCP server for C#/VB.NET. Query symbols, call graphs, and facts. 90%+ token savings.

How to run each

vbnet-lsp-claude-plugin As a Claude Code plugin

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

CodeMap

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

The marketplaces of vbnet-lsp-claude-plugin publish no settings it asks for, so we do not compare settings.

What it can do: vbnet-lsp-claude-plugin · What it can do: CodeMap · 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