Quarto MCP
The server lets AI clients create and manage temporary Quarto projects, render and inspect them, and store reusable metadata defaults.
Create temporary Quarto projects with initial files, project type, and optional config or metadata.
Render a whole project or a single input file to a chosen format (e.g. HTML, PDF), with optional code execution disabled by default.
Inspect a project or input file and get Quarto's raw inspect JSON.
Store, retrieve, and clear persistent metadata defaults (author, affiliation, ORCID, etc.) that are written into new projects as _metadata.yml.
Control server behavior with environment variables: render timeouts, output caps, storage budget, log level, and defaults file location.
Provides tools for creating temporary Quarto projects, writing project files, rendering documents or projects, inspecting Quarto configuration, and managing default metadata files.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Quarto MCP Create a Quarto project with my saved defaults and render a sample document to HTML."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Quarto MCP
A thin Model Context Protocol server that wraps the Quarto CLI.
The server creates temporary Quarto projects, writes files into them, renders them, and inspects them. It does not copy Quarto configuration logic. Quarto stays the source of truth for configuration, formats, render behavior, and inspect output.
Tools
Tool | Purpose |
| Create a temporary Quarto project and write initial files. |
| Render the project or one input file. |
| Return Quarto's inspect JSON for the project or one input file. |
| Read the stored metadata defaults and the path of their file. |
| Store the metadata defaults for every new project. |
Read SPECS.md for the full contract.
Related MCP server: overleaf-mcp-server
Requirements
Node.js 22 or later
Quarto on
PATH
Use
The server speaks MCP over stdio. Add it to a client configuration:
{
"mcpServers": {
"quarto": {
"command": "npx",
"args": ["-y", "quarto-cli-mcp"]
}
}
}To pin a version, write quarto-cli-mcp@0.2.0.
Develop
pnpm install
pnpm run buildRun the server from the clone with node /absolute/path/to/quarto-cli-mcp/dist/index.js.
A projectId is valid only while the server process runs. The server removes every temporary
project when it stops.
Remember your author details
Store your name, your affiliation, and your ORCID one time. Call quarto_defaults_set:
{
"metadata": {
"author": [
{
"name": "Ada Lovelace",
"orcid": "0000-0002-1825-0097",
"affiliations": [{ "name": "University of Basel" }]
}
],
"lang": "en",
"license": "CC BY 4.0"
}
}The server writes the value to ~/.config/quarto-cli-mcp/defaults.yml:
# Managed by quarto-cli-mcp. Written into new projects as _metadata.yml.
author:
- name: Ada Lovelace
orcid: 0000-0002-1825-0097
affiliations:
- name: University of Basel
lang: en
license: CC BY 4.0Every later quarto_create_project call copies that file into the new project as _metadata.yml.
Quarto merges _metadata.yml over _quarto.yml, so the author reaches each document.
The defaults survive a server restart. You can edit the file by hand.
To use other metadata for one project, pass metadata to quarto_create_project. The value
replaces the defaults. To skip the defaults, pass useDefaults: false. To clear the defaults,
call quarto_defaults_set with an empty metadata object.
Know these three limits
Quarto owns the merge. The server writes one file and changes nothing else.
Keep
formatout of the defaults. Aformatkey in the defaults drops the formats of the project. A project that asks forpdfthen rendershtmlonly.An author in the defaults is additive. A project that names one other author still carries the author from the defaults. To get one author list, set
useDefaults: false, or pass an explicitmetadata. Anauthorkey in a document front matter does replace the inherited list, but theauthorsspelling does not.The defaults reach the project root only. A document in
chapters/gets nothing from them. This limits their value for a book or for a manuscript.
Read the Limits section of SPECS.md for the measured table.
Server limits
Set these environment variables to change the process limits. They are server configuration, never tool parameters.
Variable | Default | Meaning |
|
| Stop a Quarto run after this time. |
|
| Cap |
|
| Temporary storage budget. |
|
| Pino log level. Logs go to stderr. |
| see below | The metadata defaults file. |
The server resolves the defaults file in this order. The first match wins:
QUARTO_MCP_DEFAULTS_FILE, then $XDG_CONFIG_HOME/quarto-cli-mcp/defaults.yml, then
~/.config/quarto-cli-mcp/defaults.yml.
Status
Version 0.2.0 is released. Read CHANGELOG.md for the history.
Security
Document code execution is off by default. --no-execute is not a sandbox. Quarto configuration
can start other programs, for example through render hooks or filters. Version 0.2 assumes
trusted project input. Use an OS or container sandbox when project input is untrusted.
Read SECURITY.md to report a vulnerability.
License
Available Tools
5 toolsquarto_create_projectCreate a Quarto projectA
Create a temporary Quarto project and write initial files into it. Returns an opaque projectId that is valid only while this server process runs.
Inputs: type, files, config, metadata, +1 more.
quarto_defaults_getRead the stored metadata defaultsA
Return the Quarto metadata that every new project receives as _metadata.yml, and the path of the file that holds it. An absent file returns empty metadata.
Inputs: no named parameters.
quarto_defaults_setStore the metadata defaultsA
Store Quarto metadata, such as author, affiliation, and ORCID, for every new project. The call replaces the whole file. Send empty metadata to clear the defaults.
Inputs: metadata (required).
quarto_inspectInspect a Quarto projectA
Return Quarto's inspect JSON for the project, or for one input file. The output is passed through without field changes.
Inputs: projectId (required), input.
quarto_renderRender a Quarto projectA
Render the project, or one input file. Code execution is off unless execute is true. A Quarto failure is reported as success: false, with stdout and stderr preserved.
Inputs: projectId (required), to, input, output, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: default metadata retrieval/set, project creation, rendering, and inspecting Quarto metadata. There is no overlap or ambiguity between the tools.
The naming pattern is mixed: defaults_get/defaults_set use noun_verb order, while create_project, render, and inspect use verb or verb_noun order. Despite the inconsistency, the names are still readable and somewhat predictable.
With 5 tools, the server is well-scoped for Quarto project management. Each tool covers a distinct necessary action without redundancy or excessive surface area.
The tool surface covers the core workflows: creating projects, rendering, inspecting metadata, and managing defaults. Minor gaps exist, such as no way to list or delete projects, but projects are temporary and the main workflow is supported.
Maintenance
Related MCP Connectors
Project management shared by people and AI agents, with persistent project state through MCP.
Design, publish and render PDF templates with Typst. Full template lifecycle over MCP.
Read project context and manage tasks in MCPBinder, with access you control.
Read and write shared BitsWeave context, projects, tasks, and work sessions through MCP.
Related MCP Servers
- AlicenseCqualityDmaintenanceEnables MCP clients to inspect, validate, test, export, and query Godot projects, including live state from an open editor via a bridge addon.2011 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents to read, write, compile, and manage Overleaf projects through MCP, including file operations, project administration, and LaTeX compilation diagnostics.16MIT
- AlicenseNot gradedqualityCmaintenanceProvides any MCP-capable coding agent with shared, warm language-server intelligence and project-local configuration, so diagnostics, definitions, references, hover, symbols, code actions, formatting, rename, and sync behave consistently across harnesses and sessions. This lets users switch agent tools without reconfiguring LSP integrations or falling back to CLI verification.MIT
- AlicenseNot gradedqualityCmaintenanceEnables clients to create, query and edit QGIS projects and vector data in an isolated, new headless PyQGIS process, exporting GeoJSON/GeoPackage, saving and reopening editable QGZ bundles, and rendering PNG maps through typed MCP tools. All operations are workspace-relative with strict path and geometry validation, and never attach to or modify a running QGIS desktop session.MIT