Document Organizer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| convert_pdfB | Convert PDF files to Markdown format using marker (recommended) or pymupdf4llm |
| discover_pdfsB | Recursively scan directory trees to locate all PDF files |
| check_conversionsC | Analyze PDF collection to determine conversion status |
| convert_missingB | Convert only PDFs that lack companion Markdown files |
| analyze_contentC | Analyze markdown files to automatically determine document categories |
| organize_structureC | Create hierarchical directory structure and move files to appropriate locations |
| full_workflowC | Execute end-to-end document organization pipeline |
| init_project_docsC | Initialize Universal Project Documentation Standard structure |
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 8 tools
Most tools have distinct purposes, but there is some overlap between 'full_workflow' and the combination of other tools like 'discover_pdfs', 'convert_pdf', and 'organize_structure', which could cause confusion about when to use the integrated workflow versus individual steps. The other tools are clearly scoped to specific tasks like analysis, conversion, discovery, and initialization.
Tool names mostly follow a consistent verb_noun pattern (e.g., analyze_content, check_conversions, convert_pdf), with 'full_workflow' as a minor deviation that uses an adjective instead of a verb. All names are in snake_case and are descriptive, making them readable and predictable, though not perfectly uniform.
With 8 tools, the count is well-scoped for a document organization server, covering key operations from discovery and conversion to analysis and structuring. Each tool appears to serve a specific function without redundancy, fitting a typical range for such a domain.
The tool set covers core document organization workflows, including discovery, conversion, analysis, and structuring, with a full pipeline tool for integration. A minor gap exists in update or delete operations for documents or categories, but agents can likely work around this given the focus on initial organization and conversion.