mcp-arabic-ms-word
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_word_documentA | Creates a new Microsoft Word (.docx) document with custom page setup, margins, metadata, and default Arabic font and RTL settings. |
| inspect_word_documentA | Parses an existing .docx file and returns structural analysis (paragraph counts, headings, tables, detected fonts, RTL flags, metadata). |
| add_paragraph_to_documentA | Appends a styled Arabic or English paragraph to a Word document with font, size, RTL, kashida justification, and line spacing. |
| add_heading_to_documentA | Appends a styled Heading (H1-H6) to a Word document with custom font size, color, alignment, and RTL support. |
| add_table_to_documentA | Appends a structured table with RTL layout (w:bidiVisual), header styling, custom cell shading, and borders to a Word document. |
| add_image_to_documentA | Embeds a PNG/JPEG image into a Word document with specified width, height, and alignment. |
| add_header_footer_to_documentA | Configures document header and footer with custom text and Arabic page numbering (صفحة X من Y). |
| modify_word_xml_elementB | Performs low-level XML text node or tag modification in document.xml for deep customization. |
| inject_template_dataA | Merges JSON key-value data into a .docx template containing tags (e.g., {name}, {#items}). |
| convert_word_to_markdownA | Extracts formatted headings and paragraph text from a Word document into structured Markdown for easy reading and analysis. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| generate-arabic-official-letter | Generates a formal Arabic official letter (خطاب رسمي) with proper RTL headers, recipient, salutation, body, and signature block. |
| generate-arabic-report | Creates a multi-page structured Arabic executive/academic report with cover page, headings, data table, and styled conclusion. |
| audit-arabic-doc-typography | Audits an existing Word document for Arabic typography standards, RTL flags, font consistency, and margin setup. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Workspace Word Documents Catalog | Dynamic JSON listing of all .docx files found within the current workspace directory. |
| Standard Arabic Document Templates Catalog | Pre-configured layout templates for Arabic official letters, administrative reports, and academic research papers. |
| Arabic Typography Font Registry | Catalog of supported Arabic fonts, recommended line heights, and fallback configurations. |
TDQS
Scored across 10 tools
Each tool targets a distinct document operation: creation, inspection, adding specific content types (paragraph, heading, table, image, header/footer), low-level XML editing, template injection, and conversion. There is no overlap between any two tools.
All tool names follow a consistent verb_noun snake_case pattern, with a clear family of 'add_X_to_document' tools. The verbs accurately describe the action and the nouns specify the target, making the set predictable.
With 10 tools, the server covers create, inspect, content addition, templating, low-level customization, and conversion. The count is well-scoped for a document manipulation server, with each tool serving a distinct purpose.
The server covers the core document lifecycle: create, inspect, add content, template injection, and conversion. Missing operations like deleting or updating existing elements are compensable via low-level XML modification, but there is no high-level remove/update tool, which is a minor gap.