Skip to main content
Glama
enesjakozh
MKhalusova

Unstructured Document Processor MCP

by MKhalusova
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

A Model Context Protocol server that provides unstructured document processing capabilities. This server enables LLMs to extract and use content from an unstructured document.

This repo is work in progress, proceed with caution :)

Supported file types:

{".abw", ".bmp", ".csv", ".cwk", ".dbf", ".dif", ".doc", ".docm", ".docx", ".dot",
 ".dotm", ".eml", ".epub", ".et", ".eth", ".fods", ".gif", ".heic", ".htm", ".html",
 ".hwp", ".jpeg", ".jpg", ".md", ".mcw", ".mw", ".odt", ".org", ".p7s", ".pages",
 ".pbd", ".pdf", ".png", ".pot", ".potm", ".ppt", ".pptm", ".pptx", ".prn", ".rst",
 ".rtf", ".sdp", ".sgl", ".svg", ".sxg", ".tiff", ".txt", ".tsv", ".uof", ".uos1",
 ".uos2", ".web", ".webp", ".wk2", ".xls", ".xlsb", ".xlsm", ".xlsx", ".xlw", ".xml",
 ".zabw"}

Prerequisites: You'll need:

Quick TLDR on how to add this MCP to your Claude Desktop:

  1. Clone the repo and set up the UV environment.

  2. Create a .env file in the root directory and add the following env variable: UNSTRUCTURED_API_KEY.

  3. Run the MCP server: uv run doc_processor.py

  4. Go to ~/Library/Application Support/Claude/ and create a claude_desktop_config.json. In that file add:

{
    "mcpServers": {
        "unstructured_doc_processor": {
            "command": "PATH/TO/YOUR/UV",
            "args": [
                "--directory",
                "ABSOLUTE/PATH/TO/YOUR/unstructured-mcp/",
                "run",
                "doc_processor.py"
            ],
            "disabled": false
        }
    }
}

  1. Restart Claude Desktop. You should now be able to use the MCP.

Available Tools

1 tool
process_documentC
Sends document to process with Unstructured, return the content of the document
 Args:
filepath: path to the document
ParametersJSON Schema
NameRequiredDescriptionDefault
filepathYes

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions processing and returning content but lacks details on permissions, rate limits, error handling, or what 'process with Unstructured' entails (e.g., parsing, extraction). For a tool with no annotations, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured: a clear purpose statement followed by a parameter explanation. It avoids unnecessary words and is front-loaded with the main functionality. The only minor inefficiency is the lack of formatting in the Args section, but overall it's efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and low schema coverage, the description is incomplete. It explains the basic operation and parameter but misses critical details like return format, error conditions, or what 'Unstructured' processing involves. For a tool that processes documents, more context is needed to use it effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description includes an Args section explaining 'filepath: path to the document', which adds meaning beyond the schema's bare title 'Filepath'. However, with 0% schema description coverage and only one parameter, this provides basic but incomplete context (e.g., no format examples or constraints). It meets the baseline for minimal parameter explanation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Sends document to process with Unstructured, return the content of the document'. It specifies the verb ('process'), resource ('document'), and technology ('Unstructured'), though it doesn't differentiate from siblings since none exist. The purpose is specific and actionable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or typical use cases. It simply states what the tool does without context about when it's appropriate. Since there are no sibling tools, this is less critical but still a gap in usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or confusion between tools. The single tool has a clear, distinct purpose of processing documents with Unstructured.

Naming Consistency5/5

The single tool name 'process_document' follows a clear verb_noun pattern. Since there is only one tool, consistency is inherently perfect with no deviations to evaluate.

Tool Count2/5

A single tool is too few for a server named 'Unstructured Document Processor MCP', which suggests broader document processing capabilities. This minimal set feels thin and under-scoped for the apparent domain.

Completeness2/5

The tool surface is severely incomplete for document processing. It only provides a basic processing function, lacking essential operations like document listing, metadata retrieval, format conversion, or batch processing, which are typical in such domains.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • MarkItDown MCP Server

    canlgz
    A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that converts various file formats (PDF, PowerPoint, Word, Excel, Images, etc.) to Markdown to make them accessible to LLMs.
    1
    MIT

  • FS-MCP Server

    boleyn
    A
    license
    Not graded
    quality
    F
    maintenance
    A Model Context Protocol server that provides intelligent file reading and semantic search capabilities across multiple document formats with security-first access controls.
    7
    MIT

  • fathom-mcp

    RomanShnurov
    A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that provides AI assistants with direct access to local document collections through full-text search, supporting multiple formats and hierarchical collections.
    MIT

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MKhalusova/unstructured-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server