Ext Ops Panel
Open dashboard
Comparison

ocrwell vs ai.extend/extend

ocrwell is a plugin bundle for AI coding tools published by ocrwell. 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: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-13. 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
Marketplaceocrwellai.extend/extend
Claude Code: claude-plugins-community Listed
Version: 18a7ad2
Forks (GitHub): 0
Stars (GitHub): 0
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

ocrwell vs ai.extend/extend
Factocrwellai.extend/extend
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (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)13
LicenceMITMIT
Repository (differs)github.com/ocrwell/skillgithub.com/extend-hq/extend-agent-plugin
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

ocrwell

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

Teaches Claude Code the OCRWell document OCR API so it generates correct integration code without having to be fed documentation. The agent learns the /v1 endpoints, the two-step upload flow (create upload → PUT to presigned URL → create document), asynchronous job polling with backoff, both structured-extraction schema formats (template and JSON Schema), the full error catalogue, rate-limit headers, and HMAC-SHA256 webhook signature verification. It also knows the quiet gotchas, like treating a 200 response carrying job.status: "failed" as a job failure rather than an HTTP success.

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

ocrwell As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install ocrwell@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.

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: ocrwell · 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