LLM Text vs llm-application-dev
llm-application-dev is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑24.
LLM Text is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). llm-application-dev is a plugin bundle for AI coding tools published by Alex Kopylov. No marketplace we read lists it any more. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Community marketplace alex-kopylov/zweihander | Not listed | Removed on 2026-10-24 Version: 0.2.3 Forks (GitHub): 0 Stars (GitHub): 8 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 Text | llm-application-devno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | No figure on GitHub | 8 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.llmtxt.dev/sse) | Installs as a plugin bundle |
| Transport (differs) | SSE | Not stated |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/alex-kopylov/zweihander |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
| Endpoint at the last check (differs) | Not responding since 2026-10-13 | no remote endpoint we check |
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 Text
Discovers and retrieves llms.txt from websites.
llm-application-dev
LLM application design, agent pattern selection, and schema-guided reasoning patterns.
How to run each
LLM Text As a remote MCP server
claude mcp add --transport sse llmtxt https://mcp.llmtxt.dev/ssellm-application-dev
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only LLM Text has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of llm-application-dev publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: LLM Text · What it can do: llm-application-dev · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.