mcp-office-parser
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| documents |
TDQS
Scored across 11 tools
Most tools have distinct targets (e.g., read_document_text vs. read_spreadsheet_data), but get_document_info and get_document_statistics could be confused, and insert_text_at_position and insert_table_docx are both insertion operations with unclear boundaries. Without descriptions, an agent might struggle to pick the right tool for metadata vs. statistics.
All tools follow a verb_noun pattern (get, read, create, insert, list, search, convert, merge), which is consistent. Minor deviations include mixing 'read' and 'get' for similar actions, and suffixes like 'at_position' vs. 'docx' are not uniform, but the overall pattern is readable.
11 tools is within the ideal 3-15 range and each tool seems to serve a distinct function in document processing. The count feels well-scoped and not bloated.
The surface covers reading, creating, inserting, converting, and merging documents, but lacks obvious operations like deleting or updating documents, and spreadsheet write capabilities are absent. This may force an agent to work around missing functionality for typical office document workflows.