minecraft-bedrock vs Plug and Ship
minecraft-bedrock is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
minecraft-bedrock is a plugin bundle for AI coding tools published by chapmanjw. No marketplace we read lists it any more. Plug and Ship is an MCP server published by plugandship.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 |  Plug and Ship | |
|---|---|---|
| Community marketplace chapmanjw/minecraft-bedrock-claude-plugin | Removed on 2026-10-18 Version: 0.6.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | minecraft-bedrockno longer listed · | Plug and Ship |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (plugandship.dev/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 23 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/chapmanjw/minecraft-bedrock-claude-plugin | github.com/plugandship/plugandship-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-15 | 2026-10-15 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 days ago |
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 minecraft-bedrock
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
anthropic-plugin-dev
Plugin development toolkit for hooks, MCP servers, commands, and skills.
-
Build high-quality MCP servers for LLM integrations
-
Build an MCP server and bundle your tools into a shareable plugin, end to end. Two skills: build-mcp scaffolds one server; build-plugin packages skills, hooks, agents, and MCP…
-
Generate MCP server scaffold and tool implementation code from a natural language description. Describe what tools you want in plain language, choose TypeScript or Python, and get…
-
Build agents, MCP servers and tool-using workflows.
-
Minecraft builds and skins made by your AI agent, live in your browser tab. Export .schem.
What each says it does
minecraft-bedrock
Guided, step-by-step setup of the Minecraft Bedrock MCP stack (dedicated server, world, behavior pack, MCP server, Claude connection) plus an in-world builder agent.
Plug and Ship
Search MCP servers, agent skills and coding-agent plugins: trending tools and best-of lists.
How to run each
minecraft-bedrock
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Plug and Ship As a remote MCP server
claude mcp add --transport http plugandship-mcp https://plugandship.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Plug and Ship has a remote endpoint we check. How we check endpoints
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: minecraft-bedrock · What it can do: Plug and Ship · 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.