wtg vs io.github.mybolide/mcp-probe-kit
wtg is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
wtg is a plugin bundle for AI coding tools published by Geoff Amey. No marketplace we read lists it any more. io.github.mybolide/mcp-probe-kit is an MCP server published by mybolide. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-27. 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
| Marketplace |  io.github.mybolide/mcp-probe-kit | |
|---|---|---|
| Community marketplace geoffamey/wtg | Removed on 2026-10-23 Version: 1.1.1 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 4.0.0 Downloads/month (npm): 1 495 Downloads/week (npm): 181 Forks (GitHub): 5 Stars (GitHub): 39 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 4.1.1 Downloads/month (npm): 1 495 Downloads/week (npm): 181 Forks (GitHub): 5 Stars (GitHub): 39 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 | wtgno longer listed · | io.github.mybolide/mcp-probe-kit |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 8 | 39 |
| Forks (GitHub) | 5 | 5 |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (mcp-probe-kit) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/geoffamey/wtg | github.com/mybolide/mcp-probe-kit |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-19 | 2026-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 wtg
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Foundational workspace — setup, context management, report parsing, inventory, template discovery, with 6 variants.
-
Plugin for Git worktree management using @desplega.ai/wts
-
Create team workspaces with shared context across multiple repos. Run /count-tongulas-workspace:create and walk through an interactive setup — enter your team name and repos, and…
-
Conventional Git automation, advanced repository management, and GitFlow workflow automation for feature, hotfix, and release branches with post-finish cleanup
-
A context layer for multi-repo workspaces. Maps features across repositories with product definitions, engineering contracts, and implementation docs — designed for AI-assisted…
-
Dev-tools — scaffold repos, multi-agent QA review, templatize. Session-handover commands and agent moved to claude-hopper in 1.2.0.
What each says it does
wtg
Install, configure, and work with wtg multi-repo feature workspaces.
io.github.mybolide/mcp-probe-kit
Spec-driven dev workflow MCP: start_* orchestration, memory, GitNexus, quality gates.
How to run each
wtg
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.mybolide/mcp-probe-kit As a local MCP server: npm package
claude mcp add --transport stdio mcp-probe-kit -- npx -y mcp-probe-kitCommands 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: wtg · What it can do: io.github.mybolide/mcp-probe-kit · 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. 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.