Ext Ops Panel
Open dashboard
Comparison

llamaparse-plugin vs ai.extend/extend

llamaparse-plugin is a plugin bundle for AI coding tools published by acrosley. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). ai.extend/extend is an MCP server published by extend.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplacellamaparse-pluginai.extend/extend
Claude Code: claude-plugins-community Listed
Version: 0.6.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
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

llamaparse-plugin vs ai.extend/extend
Factllamaparse-pluginai.extend/extend
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)2 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.extend.ai/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
LicenceMITMIT
Repository (differs)github.com/acrosley/llamaparse-plugingithub.com/extend-hq/extend-agent-plugin
Changes in the last 7 days (differs)04
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago

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

llamaparse-plugin

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

LlamaCloud document operations for Claude Code: parse, extract, classify, and split documents with LlamaIndex's hosted services, all from one plugin. Four lazy-loaded skills, each routed by name so context only enters Claude's window when needed: - llamaparse — turn PDFs, Word, PowerPoint, Excel, images, and scans into clean markdown or text via LlamaParse v2 (handles tables, multi-column layout, OCR, mixed text+images). - llamaextract — pull structured JSON out of a document against a JSON Schema you supply (invoice line items, contract terms, form fields, entities). - llamaclassify — categorize a document into one of a defined set of labels with a confidence score and a short reasoning string. - llamasplit — break a long document into typed sections with page ranges and per-section confidence (LlamaSplit v1 beta). Includes a standalone `llamaparse` CLI (`parse / extract / classify / split` subcommands plus `doctor` for preflight checks) so the same code powers scripts, CI jobs, and the Claude Code skills. R

ai.extend/extend

In its own words, on Official MCP Registry:

Turn documents into structured data: parse, extract, classify, split, and fill PDF forms.

How to run each

llamaparse-plugin As a Claude Code plugin

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

ai.extend/extend As a remote MCP server

Claude Code
claude mcp add --transport http extend https://mcp.extend.ai/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only ai.extend/extend 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: llamaparse-plugin · What it can do: ai.extend/extend · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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