MCP LaTeX Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LATEX_BASE_PATH | No | The base directory path where the server will manage and access LaTeX files. | |
| LATEX_LOG_LEVEL | No | The level of logging detail. Possible values: DEBUG, INFO, WARNING, ERROR. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_latex_fileC | Create a new LaTeX document with specified content and structure. |
| create_from_templateB | Create a LaTeX document from a bundled template file. |
| edit_latex_fileB | Edit an existing LaTeX file by replacing, inserting, or appending content. |
| read_latex_fileB | Read and return the contents of a LaTeX file. |
| list_latex_filesB | List all .tex files in a directory. |
| validate_latexB | Perform LaTeX syntax validation (structure, braces, environments, references). |
| get_latex_structureA | Extract document structure: class, title, author, packages, and section hierarchy. |
| compile_latexB | Compile a LaTeX file to PDF using the specified engine. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_templates | List available LaTeX templates. |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no ambiguity: compile, create from template, create new file, edit file, get structure, list files, read file, and validate syntax. The descriptions reinforce unique functions, preventing misselection.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., compile_latex, edit_latex_file). This predictability makes the set easy to navigate and understand.
With 8 tools, the server is well-scoped for LaTeX document management. Each tool earns its place by covering essential operations like creation, editing, reading, validation, and compilation without bloat.
The toolset provides strong coverage for core LaTeX workflows, including CRUD operations and validation. A minor gap is the lack of tools for managing bibliographies or handling complex LaTeX errors, but agents can work around this with existing tools.