tech-lead-planning vs vlm-code-context-mcp
tech-lead-planning is a plugin bundle for AI coding tools published by Seth Ford. Marketplaces we read that list it: 1 (Community GitHub marketplaces). vlm-code-context-mcp is an MCP server published by VelimirMueller. Marketplaces we read that list it: 1 (npm registry (MCP servers)). As of our marketplace pass on 2026-11-08. 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
| Marketplace |  vlm-code-context-mcp | |
|---|---|---|
| Community marketplace sethdford/claude-skills | Listed Version: 1.0.0 Forks (GitHub): 9 Stars (GitHub): 47 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Not listed | Listed Version: 3.0.1 Downloads/month (npm): 2 683 Downloads/week (npm): 2 132 Forks (GitHub): 2 Stars (GitHub): 5 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
| Fact | tech-lead-planning | vlm-code-context-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 47 (better) | 5 (worse) |
| Forks (GitHub) (differs) | 9 (better) | 2 (worse) |
| Last release (differs) | Not published | 2026-10-22 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (vlm-code-context-mcp) |
| Transport | Not stated | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 13 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/sethdford/claude-skills | github.com/velimirmueller/code-context-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-11-05 | 2026-10-12 |
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
tech-lead-planning
Technical roadmaps, estimation, sprint planning, capacity planning, dependency mapping.
vlm-code-context-mcp
AI-powered virtual IT department via MCP — codebase intelligence, 9-agent scrum team, sprint management, and React dashboard in one npm package
How to run each
tech-lead-planning As a Claude Code plugin
/plugin marketplace add sethdford/claude-skills
/plugin install tech-lead-planning@claude-skillsvlm-code-context-mcp
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: tech-lead-planning · What it can do: vlm-code-context-mcp · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.