dream-team vs GodPrompt MCP Server
dream-team is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
dream-team is a plugin bundle for AI coding tools published by DreamTeam. No marketplace we read lists it any more. GodPrompt MCP Server is an MCP server published by AKzar1el. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 | ||
|---|---|---|
| Community marketplace abssoft/dreamteam | Removed on 2026-10-15 Version: 7.5.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.39 Forks (GitHub): 1 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
| Fact | dream-teamno longer listed · | GodPrompt MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 0 | 1 |
| Forks (GitHub) (differs) | 0 | 1 |
| Last release (differs) | Not published | 2026-10-25 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (god-prompt-mcp.tomi-seregi99.workers.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) | 8 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/abssoft/dreamteam | github.com/akzar1el/god-prompt-mcp |
| Changes in the last 7 days (differs) | 0 | 12 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 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 dream-team
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Team-process conventions shared by the sdlc and code-review plugins — the workflow-identify skill that resolves the tracker, team and state names at run time, and the…
-
Developer experience and team collaboration tools including onboarding automation, documentation generation, async standups with Linear integration, and knowledge management
-
Engineering workflow skills: team-code-review, stacked-prs, conventional-comments, conventional-commits, and tdd.
-
Software delivery workflow commands — gather context, write plans, file tickets, open MRs, babysit them to green, wrap them up, and brief next steps
-
Codely's team skills: planning, docs, OpenSpec, and git conventions.
-
Core agents and commands required by all plugins
What each says it does
dream-team
Tracker-neutral professional skills for project-owned SDLC workflows.
GodPrompt MCP Server
GodPrompt MCP + Agent Skill for coding agents with TDD, debugging, verification, and task routing.
How to run each
dream-team
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
GodPrompt MCP Server As a remote MCP server
claude mcp add --transport http god-prompt-mcp https://god-prompt-mcp.tomi-seregi99.workers.dev/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only GodPrompt MCP Server 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: dream-team · What it can do: GodPrompt MCP Server · 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.