Mammoth 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_docx_to_htmlC | Convert a DOCX file to HTML using mammoth. Supports reading from a file path and returns the HTML content. |
| convert_docx_to_html_with_imagesA | Convert a DOCX file to HTML with embedded images as base64 data URIs |
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 2 tools
The two tools have highly overlapping purposes—both convert DOCX to HTML—with the only difference being image handling. An agent could easily misselect between them, as the distinction is subtle and not clearly differentiated in the names alone. This creates ambiguity about which tool to use for a given conversion task.
Both tools follow a consistent verb_noun pattern with 'convert_docx_to_html' as the base, and the second tool adds a descriptive suffix '_with_images'. The naming is predictable and clear, using snake_case uniformly without any deviations or mixed conventions.
With only 2 tools, the server feels thin and under-scoped for a 'Mammoth MCP Server' that implies broader DOCX processing capabilities. This minimal set lacks basic operations like converting to other formats (e.g., Markdown, plain text) or handling DOCX metadata, making it inadequate for comprehensive document conversion tasks.
The tool surface is severely incomplete for a DOCX conversion server. It only covers HTML output with two variants, missing essential operations such as conversion to other formats (e.g., PDF, Markdown), extraction of text or images separately, or handling of DOCX properties. This will cause agent failures when broader document processing is needed.