Ext Ops Panel
Open dashboard
Comparison

LLM Text vs llamaparse

LLM Text is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). llamaparse is a plugin bundle for AI coding tools published by run-llama. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-15. 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
MarketplaceLLM Textllamaparse
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 8669edf
Forks (GitHub): 1
Stars (GitHub): 4
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

LLM Text vs llamaparse
FactLLM Textllamaparse
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub4
Forks (GitHub) (differs)No figure on GitHub1
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.llmtxt.dev/sse)Installs as a plugin bundle
Transport (differs)SSENot stated
Tools it declares (differs)2Not published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/run-llama/llamaparse-agent-plugins
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-13no remote endpoint we check

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

LLM Text

In its own words, on Docker MCP Catalog:

Discovers and retrieves llms.txt from websites.

llamaparse

In its own words, on Claude Code: claude-plugins-community:

Connect your agents to the entire LlamaParse stack, from local parsing with LiteParse to cloud-powered workflows with LlamaParse and its MCP

How to run each

LLM Text As a remote MCP server

Claude Code
claude mcp add --transport sse llmtxt https://mcp.llmtxt.dev/sse

llamaparse As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install llamaparse@claude-community

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 llamaparse 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: llamaparse · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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