WordCraft MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORDCRAFT_APP | No | Path of the desktop app when it lives elsewhere (e.g. a Linux AppImage) | |
| WORDCRAFT_CLI | No | Path of wordcraft-cli / wordcraft-cli.exe (wins over WORDCRAFT_DIR) | |
| WORDCRAFT_DIR | No | WordCraft folder, one of its executables, a .tar.gz root (with bin/) or WordCraft.app. Default: auto-detect | |
| WORDCRAFT_MCP_TIMEOUT | No | Maximum seconds per engine call (default 3600) | 3600 |
| WORDCRAFT_CONTROL_PORT | No | Control port of the desktop app (default 7985) | 7985 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_documentA | Write a new document with WordCraft (a Word-class word processor): headings, paragraphs with styles and formatting, bullet / numbered lists, tables, images with captions, page breaks, a table of contents and footnotes, plus page size, margins, headers, footers and page numbers. Starts blank or from a built-in template (letter, resume, report). Saves docx, pdf, odt, rtf, html, md, tex, txt or png pages in one go, and returns a preview of page 1. |
| edit_documentA | Edit existing documents (docx, doc, odt, rtf, md, html, txt...) without touching the originals: find and replace (with match case / whole word / wildcards), comments on found text, tracked changes (so every edit is reviewable in Word), accept or reject existing revisions, append content blocks (same blocks as create_document), change properties, page setup and headers / footers, and remove personal information. Saves "_edited." (or the formats asked for) next to each input or in output_dir. |
| mail_mergeA | Personalized letters, certificates or notices from a data file (CSV, TSV, TXT, XLSX, ODS): either a template document that already has merge fields, or a body written here with {{Field}} placeholders (the column names). Writes one merged document with a section per record (docx, and pdf / other formats if asked). |
| convert_documentA | Convert one or many documents between docx, doc (read), pdf, odt, rtf, html, md, tex, txt, json and png (first page) with WordCraft. markup=true prints comments and tracked changes (Print Markup). Outputs go next to each input or into output_dir; nothing is replaced unless overwrite is true. |
| get_document_infoB | Pages, words, paragraphs, sections, comments, tracked changes and properties of documents; optionally the structure (headings, paragraph styles, lists, tables with cell texts) to understand a document before editing it. |
| extract_textA | Plain text of documents (docx, doc, odt, rtf, html, md, pdf made by WordCraft...). Returns the text (up to max_chars per document) and, with save_txt, also writes .txt files. |
| render_pagesA | Render document pages to PNG to look at them: returns up to 4 page images and, with save=true, writes _p.png files. |
| list_wordcraft_catalogA | What WordCraft can do: commands (615 engine commands with parameters and ribbon location, for run_wordcraft_commands), styles (paragraph, character and table styles of a new document or of input_path), templates (new document templates), formats (open and save). |
| run_wordcraft_commandsA | Advanced: run any of WordCraft's 615 engine commands in order (text., format., para., styles., table., insert., layout., references., review., mailings., design., equation., chart., smartArt., fields.*...) plus the engine tools new_document / open_document / type_text / select_text / get_text / inspect_document / render_page / save_document (step id = the tool name), on a new document, a template or an opened file, then save. Parameters can use "$steps[N].field" for a value returned by step N (0-based). With live=true the steps drive the open WordCraft app instead. |
| open_in_wordcraftA | Open documents in the WordCraft desktop app for manual editing. With control=true the app also starts its loopback-only control channel (protected by a key in WordCraft's settings folder) so run_wordcraft_commands live=true can drive it. |
| get_wordcraft_statusA | Check the WordCraft installation: platform, executables, version, engine commands, Word feature coverage, save formats, whether the app is running / listening for control. |
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 11 tools
High-level tools map cleanly to distinct document actions: create, edit, convert, inspect, extract, render, mail merge, and app control are easy to tell apart. The main overlap is run_wordcraft_commands, which exposes low-level equivalents of several higher-level tools, but its 'Advanced' framing and the catalog tool keep the boundary reasonably clear.
All names use snake_case consistently, and most follow a verb-first pattern such as create_document, convert_document, and get_wordcraft_status. Minor deviations like mail_merge and open_in_wordcraft are readable but slightly less pattern-conforming.
Eleven tools is well within the ideal range and matches the broad document-processing purpose. Each tool covers a meaningful capability without obvious bloat.
The surface covers the full document lifecycle: creation, editing, conversion, metadata inspection, text extraction, rendering, mail merge, advanced command execution, desktop integration, and status checks. No significant workflow gap is apparent for a Word-class document server.