llm-application-dev vs io.github.Medhovarsh/forkmind
llm-application-dev is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑24.
llm-application-dev is a plugin bundle for AI coding tools published by Alex Kopylov. No marketplace we read lists it any more. io.github.Medhovarsh/forkmind is an MCP server published by Medhovarsh. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-26. 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 alex-kopylov/zweihander | Removed on 2026-10-24 Version: 0.2.3 Forks (GitHub): 0 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.9.0 Downloads/month (npm): 240 Downloads/week (npm): 30 Forks (GitHub): 0 Stars (GitHub): 3 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 | llm-application-devno longer listed · | io.github.Medhovarsh/forkmind |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 8 | 988 |
| Forks (GitHub) (differs) | 0 | 789 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (forkmind) |
| 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 | 4 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/alex-kopylov/zweihander | github.com/medhovarsh/forkmind |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 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 llm-application-dev
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
LLM application development, prompt engineering, and AI assistant optimization
-
LLM application development, prompt engineering, and AI assistant optimization
-
AI / LLM application engineering expertise. Ships the ai-engineer agent plus the in-house ai-app-templates skill and 1 vendored skill (senior-prompt-engineer) for production LLM…
-
ai
Build production-grade AI agents with Pydantic AI — tools, capabilities, structured output, streaming, and testing patterns — and port existing agents over from LangChain, the…
-
10 AI agent engineering skills: knowledge base injection, entity memory, multi-model routing, proactive intelligence, MCP servers, parallel orchestration
-
Dynamic Agentic Architecture with cognitive patterns, knowledge sharing, and adaptive agents
What each says it does
llm-application-dev
LLM application design, agent pattern selection, and schema-guided reasoning patterns.
io.github.Medhovarsh/forkmind
Branchable LLM history DAG + encrypted context capsules agents can save, restore, and crypto-shred.
How to run each
llm-application-dev
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.Medhovarsh/forkmind As a local MCP server: npm package
claude mcp add --transport stdio forkmind -- npx -y mcp forkmind
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: llm-application-dev · What it can do: io.github.Medhovarsh/forkmind · 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.