llamaparse vs io.github.IntelagentStudios/mcp-file-processor
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). io.github.IntelagentStudios/mcp-file-processor is an MCP server published by IntelagentStudios. 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
| Marketplace |  llamaparse |  io.github.IntelagentStudios/mcp-file-processor |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 8669edf Forks (GitHub): 1 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.1 Downloads/month (npm): 155 Downloads/week (npm): 34 Forks (GitHub): 0 Stars (GitHub): 0 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 | llamaparse | io.github.IntelagentStudios/mcp-file-processor |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 4 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@intelagent/mcp-file-processor) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/run-llama/llamaparse-agent-plugins | github.com/intelagentstudios/intelagent-mcps |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
Connect your agents to the entire LlamaParse stack, from local parsing with LiteParse to cloud-powered workflows with LlamaParse and its MCP
io.github.IntelagentStudios/mcp-file-processor
Text extraction, keyword extraction, language detection, and chunking for RAG
How to run each
llamaparse As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install llamaparse@claude-communityio.github.IntelagentStudios/mcp-file-processor As a local MCP server: npm package
claude mcp add --transport stdio mcp-file-processor -- npx -y @intelagent/mcp-file-processorCommands 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: llamaparse · What it can do: io.github.IntelagentStudios/mcp-file-processor · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.