One MCP, Many Parsers
Let your coding agent parse PDFs, Office files, and messy documents through one MCP that picks markitdown, Docling, or LlamaParse automatically.
Overview
parse-mcp is a MCP server for the Build phase that routes document parsing across markitdown, Docling, and LlamaParse plus an interpret tool for agent-ready text.
What is this MCP server?
- Single MCP entry point routes requests across markitdown, Docling, and LlamaParse backends
- Optional LlamaParse path when you need cloud parsing (LLAMAPARSE_API_KEY only for that route)
- Interpret tool layers meaning on top of raw extracted text for agent follow-up questions
- stdio transport via released .mcpb bundle (v0.1.0) for Claude Code–style hosts
- Fits solo-builder doc-to-context workflows without maintaining three separate integrations
- 3 named parser backends: markitdown, Docling, and LlamaParse
- Server schema version 0.1.0 with stdio .mcpb distribution
- 1 optional secret env var: LLAMAPARSE_API_KEY for LlamaParse routing only
What problem does it solve?
Solo builders waste cycles swapping parser libraries and API keys every time a new file type shows up in a RAG or import pipeline.
Who is it for?
Indie builders adding document upload, knowledge bases, or spec ingestion to agent workflows who want parser choice without three MCPs.
Skip if: Teams that only need plain Markdown from repos and never touch PDFs, scans, or Office binaries.
What do I get? / Deliverables
After you register parse-mcp, your agent can parse and interpret heterogeneous documents through one MCP without you re-plumbing parsers per project.
- Unified parse and interpret tool calls from your agent across multiple parser backends
- Extracted text suitable for embeddings, summaries, or codegen context
- Configurable fallback to LlamaParse for harder document layouts
Recommended MCP Servers
Journey fit
Document ingestion lands in Build when you wire RAG, importers, or spec pipelines—not when you are only brainstorming. Integrations is the right shelf because this server is a router between multiple third-party parsers, not a standalone app feature.
How it compares
MCP document-router integration, not a hosted parsing SaaS or a single-library skill.
Common Questions / FAQ
Who is parse-mcp for?
Solo and indie developers using Claude Code, Cursor, or Codex who need reliable multi-format document text for RAG, imports, or planning from PDFs and Office files.
When should I use parse-mcp?
Use it during Build when you connect file uploads or external docs to your agent and want automatic routing between markitdown, Docling, and optional LlamaParse.
How do I add parse-mcp to my agent?
Install the v0.1.0 .mcpb release, configure stdio in your MCP client, set LLAMAPARSE_API_KEY only if you route jobs to LlamaParse, then enable the server in Claude Code or Cursor.