Quario

What quario does

The quario MCP server turns a JSON report definition and data into one of five output formats: PDF, Excel (xlsx), Word (docx), HTML, or CSV. A single definition can be used across targets, while target-specific validation checks whether required features are available for the selected format.

It exposes two MCP tools. validate_report examines a definition without producing a file and returns problems and warnings with locations such as JSON paths. render_report validates and renders one target, writes the result to disk, and returns the path and size. The response contains a path rather than the generated file bytes, which keeps large reports out of the model context.

How it works

The client launches the package as a local stdio process. An agent supplies a report definition to validate_report, corrects any reported issues, and then calls render_report with a target and either inline JSON data or a dataPath. The latter must refer to a JSON file inside the configured data root.

Rendering can receive parameters, a locale, currency, time zone, filename, and target options. If the requested filename already exists, the server adds numeric suffixes such as -1 and -2 instead of overwriting it. The host controls query limits, permitted link schemes, data access, and output location through environment variables; tool calls cannot change those host settings.

Setup and configuration

Node.js 22 or newer is required. The package can be started with npx -y @quario/mcp, and it can be registered with Claude Desktop or Claude Code using a stdio MCP configuration. No separate installation is needed for the rendering targets because the package includes them.

The quario MCP server uses environment variables rather than command-line flags or a configuration file. QUARIO_OUT_DIR selects the output directory, while QUARIO_DATA_ROOT controls where dataPath can resolve. Without an output setting, files go under a quario-mcp directory in the system temporary area. Claude Code's project directory is used as the data root when QUARIO_DATA_ROOT is unset and that project variable is available.

Other settings provide defaults for locale, currency, and time zone, and configure query depth, node, and result budgets. QUARIO_SCHEMES controls permitted href schemes. Invalid runtime settings can stop startup. A missing or invalid license key does not stop startup, but rendered output carries an unlicensed mark. The MCP package is Apache-2.0; the bundled engine and render targets use the Quario License, with free evaluation.

Tools and capabilities

• validate_report: checks a report definition and optionally evaluates requirements against selected targets.
• render_report: renders one definition to html, pdf, xlsx, docx, or csv.
• Returns structured and textual problem and warning data for client compatibility.
• Supports inline JSON data or a JSON file addressed through dataPath.
• Accepts report parameters and presentation settings such as locale, currency, and time zone.
• Writes files locally and reports their paths and sizes.

The definition carries the report schema and can describe data selection, columns, and calculated values. Diagnostics may include a path, message, source, code, and source positions when available.