Ext Ops Panel
Open dashboard
Comparison

Effect vs GodPrompt MCP Server

Effect is an MCP server published by tim-smart. Marketplaces we read that list it: 1 (Docker MCP Catalog). GodPrompt MCP Server is an MCP server published by AKzar1el. Marketplaces we read that list it: 2 (Official MCP Registry, 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

Where each is published
MarketplaceEffectGodPrompt MCP Server
Docker MCP Catalog Listed
Version: sha256:a0e077abc890
Forks (GitHub): 13
Pulls (Docker Hub): 13 362
Stars (Docker Hub): 0
Stars (GitHub): 238
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.44
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.0.44
Downloads/month (npm): 3 947
Downloads/week (npm): 3 229
Forks (GitHub): 1
Stars (GitHub): 2
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

Effect vs GodPrompt MCP Server
FactEffectGodPrompt MCP Server
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)238 (better)2 (worse)
Pulls (Docker Hub) (differs)13 362No figure on Docker Hub
Forks (GitHub) (differs)13 (better)1 (worse)
Last release (differs)Not published2026-10-27
Where it runs (differs)On your machine (mcp/effect-mcp)Remote server or your machine
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)2Not published
Environment variables it asks forNot publishedNot published
LicenceMITMIT
Repository (differs)github.com/tim-smart/effect-mcpgithub.com/akzar1el/god-prompt-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 32 h ago returned HTTP 405

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

Effect

In its own words, on Docker MCP Catalog:

Tools and resources for writing Effect code in Typescript.

GodPrompt MCP Server

In its own words, on Official MCP Registry:

GodPrompt MCP + Agent Skill for coding agents with TDD, debugging, verification, and task routing.

How to run each

Effect As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio effect-mcp -- docker run -i --rm mcp/effect-mcp

GodPrompt MCP Server As a remote MCP server

Claude Code
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

Only Effect has

  • effect_docs_search
  • get_effect_doc

Only GodPrompt MCP Server has

  • classify_task
  • get_anti_patterns
  • get_core_skill
  • get_gates
  • get_god_prompt
  • get_protocols
  • get_version

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (GodPrompt MCP Server as of 2026-11-06). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Effect · What it can do: GodPrompt MCP Server · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. 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