Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
VERIFIED_DOCX_MCP_ALLOWED_FILE_ROOTSNoColon-separated list of allowed file roots for path safety. Defaults to the user's home directory. This allowlist is used to resolve path arguments.User's home directory

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
export_pdfA

Render a local .docx to PDF via Microsoft Word and report its page count.

output_path must fall inside VERIFIED_DOCX_MCP_ALLOWED_FILE_ROOTS (defaults to the user's home directory), must not resolve to a credential path, and its parent directory must already exist. This is a read/render tool: the source .docx is never modified (Word opens a private staged copy — see render.py), so the return value has no "applied" key.

Returns pdf_path, sha256, page_count (best-effort; None — never a guessed 0 — when it cannot be determined), page_count_source ("word"|"pdfinfo"|"regex"|None), engine ("word"; the only engine, D2: no LibreOffice), and left_open_document (the rendered document's window title in Word — see render.py's module docstring for why it is never auto-closed).

Errors: INVALID_INPUT - a bad path or output_path RENDER_ENGINE_UNAVAILABLE - no render engine available (Word only) AUTOMATION_NOT_GRANTED - macOS declined Automation control of Word for this app; run verified-docx-mcp doctor for the fix, scoped to the app hosting this MCP server's own process WORD_SANDBOX_UNAVAILABLE - Word has never been launched on this machine (its sandbox container does not exist yet) RENDER_FAILED - any other Word automation failure

lock_statusA

Report Word/LibreOffice owner-file presence and sync-quiesce state.

Data only — never refuses. Owner-file detection recognizes Word's "~$" owner file (matched by shared filename suffix, not by constructing one exact expected name — see _word_owner_file_matches's docstring) and LibreOffice's ".~lock.#". Sync-quiesce takes two (size, mtime_ns) samples ~1.5s apart and also checks for ".tmp"/".~*" siblings in the same directory (OneDrive/iCloud staging artifacts); "sync_quiesced" is false if either signal suggests the file is still being written.

Returns path, owner_file ({present, path, format, owner_name}), sync_quiesced, sync_detail ({sample_1, sample_2, interval_seconds, tmp_siblings}).

Errors: INVALID_INPUT - path does not exist or is outside the allowed roots

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources