Connections & Capabilities
Connects To
Capabilities
Quickstart
Config
{
"mcpServers": {
"typst": {
"command": "docker",
"args": [
"run", "--rm", "-i",
"ghcr.io/johannesbrandenburger/typst-mcp:latest"
]
}
}
}Exposed MCP Tools (5)
list_docs_chapters()Lists all chapters available in the Typst documentation.
Read-only access to documentation content.
get_docs_chapter(route)Retrieves the content of a specific chapter from the Typst documentation.
Read-only access to documentation content.
latex_snippet_to_typst(latex_snippet)Converts a LaTeX code snippet into Typst code using Pandoc.
Conversion process may introduce vulnerabilities or unexpected behavior.
check_if_snippet_is_valid_typst_syntax(typst_snippet)Validates whether a given Typst code snippet has correct syntax.
Performs syntax checking without executing the code.
typst_to_image(typst_snippet)Renders a Typst code snippet into a PNG image.
Image rendering can consume significant resources and potentially expose vulnerabilities.
Safety Assessment
The Typst MCP server is relatively safe for read-only operations like documentation access. However, the LaTeX conversion and Typst code execution tools introduce moderate risks, especially if user inputs are not carefully validated. Running the server in a sandboxed environment like Docker is recommended.
- No direct access to the host filesystem.
- Typst code execution is sandboxed.
- Limited toolset reduces attack surface.
- Read-only documentation access.
- Potential for code injection via LaTeX conversion.
- Typst code execution, even sandboxed, carries some risk.
- Image generation could be used to create misleading content.
- Server execution relies on external dependencies (Pandoc, Typst).
