---
type: "post"
id: "parse-extract-classify-now-each-with-its-own-dc0f04"
slug: "parse-extract-classify-now-each-with-its-own-dc0f04"
title: "Parse, Extract, Classify — now each with its own MCP"
description: "LlamaIndex is moving document agents toward a decomposed and more inspectable operating model."
retrieval_nugget: "LlamaIndex is moving document agents toward a decomposed and more inspectable operating model."
published_at: "2026-09-25"
updated_at: "2026-09-25"
record_date: "2026-09-25"
date_kind: "published_at"
topics: []
source_urls: ["https://www.llamaindex.ai/blog/llamaindex-newsletter-26-07-08"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:parse-extract-classify-now-each-with-its-own-dc0f04"
status: "published"
visuals: []
editorial_provenance: {"schema_version":"newruntime-editorial-copy-v1","content_status":"source_grounded_final","final_copy_sha256":"sha256:2fe508f0b8048e4c9d9355061d2e7c8b196ad89bf319d186090ffb3906874f47","reviewed_at":"2026-09-25T20:05:00.485Z","source_evidence_count":1,"verified_claim_count":2,"site_analysis_schema_version":"newruntime-site-analysis-v1","site_object_kind":"field_note","observed_fact_count":2,"implication_count":2,"watch_condition_count":2,"related_record_count":0}
analysis: {"schema_version":"newruntime-site-analysis-v1","object_kind":"field_note","thesis":"LlamaIndex is turning document processing from a single retrieval call into a more modular, inspectable agent workflow.","observed_facts":[{"text":"LlamaParse Retrieval Harness provides list, grep, read, and hybrid-retrieve tools for agents working across a corpus.","source_urls":["https://www.llamaindex.ai/blog/llamaindex-newsletter-26-07-08"]},{"text":"LlamaIndex now offers one general MCP endpoint plus separate endpoints for Parse, Extract, Classify, Split, and Index.","source_urls":["https://www.llamaindex.ai/blog/llamaindex-newsletter-26-07-08"]}],"mechanism":"Filesystem-style retrieval lets an agent enumerate files, use lexical search where appropriate, read source material, and combine that work with hybrid retrieval; task-specific MCP endpoints restrict the available tool surface to the operation at hand.","why_now":"As document agents move into larger enterprise workflows, teams need both more reliable evidence access and a way to attribute processing spend by team, environment, customer, or product line.","implications":["Teams can design workflows that separate parsing, extraction, classification, retrieval, and verification rather than treating document intelligence as one opaque step.","Usage Tags, user metadata, and improved tier routing make cost a controllable dimension of the workflow rather than only an aggregate bill."],"evidence_boundary":"These are vendor-reported product capabilities and performance claims; the supplied source does not provide independent reliability results, comparative cost data, or production error rates.","watch_conditions":["Watch whether LlamaIndex publishes evidence that narrower MCP surfaces and Retrieval Harness reduce retrieval or citation failures in real deployments.","Watch whether the distinct endpoints gain ecosystem support in automation and agent frameworks."],"related_records":[],"new_branch_reason":"The supplied related references contain no readable prior New Runtime record, while this source documents a distinct release bundle centered on retrieval control, MCP segmentation, and document-processing cost governance."}
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/parse-extract-classify-now-each-with-its-own-dc0f04/","markdown":"https://newruntime.com/posts/parse-extract-classify-now-each-with-its-own-dc0f04.md","json":"https://newruntime.com/posts/parse-extract-classify-now-each-with-its-own-dc0f04.json"}
---

# Parse, Extract, Classify — now each with its own MCP

## Retrieval answer

LlamaIndex is moving document agents toward a decomposed and more inspectable operating model.

LlamaIndex is moving document agents toward a decomposed and more inspectable operating model. The core shift is from asking one retrieval system for an answer to giving an agent bounded ways to explore, search, read, and verify its source corpus. The announcement is consequential because it connects retrieval behavior, tool exposure, and processing-cost attribution in one product surface.

Thesis: LlamaIndex is turning document processing from a single retrieval call into a more modular, inspectable agent workflow. Observed facts: LlamaParse Retrieval Harness provides list, grep, read, and hybrid-retrieve tools for agents working across a corpus. Observed facts: LlamaIndex now offers one general MCP endpoint plus separate endpoints for Parse, Extract, Classify, Split, and Index. Mechanism: Filesystem-style retrieval lets an agent enumerate files, use lexical search where appropriate, read source material, and combine that work with hybrid retrieval; task-specific MCP endpoints restrict the available tool surface to the operation at hand. Why now: As document agents move into larger enterprise workflows, teams need both more reliable evidence access and a way to attribute processing spend by team, environment, customer, or product line.

Implications: Teams can design workflows that separate parsing, extraction, classification, retrieval, and verification rather than treating document intelligence as one opaque step. Implications: Usage Tags, user metadata, and improved tier routing make cost a controllable dimension of the workflow rather than only an aggregate bill. Evidence boundary: These are vendor-reported product capabilities and performance claims; the supplied source does not provide independent reliability results, comparative cost data, or production error rates. Watch conditions: Watch whether LlamaIndex publishes evidence that narrower MCP surfaces and Retrieval Harness reduce retrieval or citation failures in real deployments. Watch conditions: Watch whether the distinct endpoints gain ecosystem support in automation and agent frameworks.

New branch reason: The supplied related references contain no readable prior New Runtime record, while this source documents a distinct release bundle centered on retrieval control, MCP segmentation, and document-processing cost governance.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)