Unstructured Document Processor MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_KEY | Yes | AWS access key for authentication | |
| AWS_SECRET | Yes | AWS secret key for authentication | |
| AWS_S3_SOURCE_BUCKET | Yes | S3 bucket used as a source of documents in the processing workflow | |
| UNSTRUCTURED_API_KEY | Yes | API key for Unstructured Platform | |
| AWS_S3_DESTINATION_BUCKET | Yes | S3 bucket used as a destination for processed documents |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| process_documentC | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
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.
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.
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.