Ext Ops Panel
Open dashboard
Comparison

ai.filegraph/document-processing vs image-ocr

ai.filegraph/document-processing is an MCP server published by filegraph.ai. Marketplaces we read that list it: 1 (Official MCP Registry). image-ocr is an MCP server published by ocr.kymac.co. Marketplaces we read that list it: 1 (Official MCP Registry). 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
Marketplaceai.filegraph/document-processingimage-ocr
Official MCP Registry Listed
Version: 1.0.1
No figure published
Not marked · First seen
Listed
Version: 0.4.0
No figure published
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

ai.filegraph/document-processing vs image-ocr
Factai.filegraph/document-processingimage-ocr
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.filegraph.ai/mcp)Remote server (ocr.kymac.co/mcp)
Transport (differs)SSEStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/filegraph/docconvertNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 38 h agoNot responding since 2026-10-15

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

ai.filegraph/document-processing

In its own words, on Official MCP Registry:

Extract text from documents, manipulate PDFs, and perform OCR on images.

image-ocr

In its own words, on Official MCP Registry:

Image URL → plain text OCR for bots. Free try then prepaid TEST. https://ocr.kymac.co

How to run each

ai.filegraph/document-processing As a remote MCP server

Claude Code
claude mcp add --transport sse document-processing https://api.filegraph.ai/mcp

image-ocr As a remote MCP server

Claude Code
claude mcp add --transport http image-ocr https://ocr.kymac.co/mcp --header "Authorization: Bearer <YOUR_TOKEN>" --header "X-API-Key: <YOUR_X_API_KEY>"

Requires: Authorization header, X-API-Key header

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

Only the endpoint of ai.filegraph/document-processing responded at the last daily 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: ai.filegraph/document-processing · What it can do: image-ocr · Compare two other plugins

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.

Where the data comes from: how the catalog is built