quario MCP server

@quario/mcp

Let an agent turn JSON data into a PDF, Excel, Word, HTML or CSV report. This MCP server gives Claude and other MCP clients two tools. validatereport checks a report definition, and renderreport writes it to a file. One definition renders to all five formats, and the agent gets back a path, never the file's bytes.

data: expected a JSONPath string. The agent repairs that spot and tries again.

• Five formats. One JSON definition renders to pdf, xlsx, docx, html and csv.
• Fixable errors. Each problem names the path it sits at, such as

costs the agent one line of context, whatever its size.

• Files, not bytes. render_report writes to disk and returns the path and size. A report

directory come from the launch configuration. No tool argument changes them.

• The host stays in charge. Query budgets, link schemes, the data root and the output

• No overwrites. A name that exists gets -1, then -2, and so on.
• Local. It runs over stdio, and npx @quario/mcp starts it.

A render_report call and its result:

{
  "definition": {
    "data": "$.orders[*]",
    "detail": { "columns": [{ "header": "Total", "value": "{{ @.price * @.qty }}" }] }
  },
  "target": "pdf",
  "data": { "orders": [{ "price": 250, "qty": 2 }] },
  "filename": "orders"
}

The tool answers Wrote orders.pdf (1.3 kB): /tmp/quario-mcp/orders.pdf.

The server is open source. The engine it runs is not. This package is Apache-2.0. It installs

quario and the five render targets. Those packages are

commercial software under the Quario License. Evaluation is free.

Without a license key, every render carries an unlicensed mark.

Contents

• Getting started
• Configuration
• The trust line
• validate_report
• render_report
• Not in this release
• Development
• License

Getting started

1. Check Node. The server needs Node 22 or later.

node --version

2. Add the server to your client. The package carries the engine and the five render targets, so there is nothing else to install.

Claude Code, for evaluation without a key:

claude mcp add quario -- npx -y @quario/mcp

Claude Code, with a license key:

claude mcp add quario -e QUARIO_LICENSE=quario_... -- npx -y @quario/mcp

Claude Desktop, in claudedesktopconfig.json:

{
  "mcpServers": {
    "quario": {
      "command": "npx",
      "args": ["-y", "@quario/mcp"],
      "env": { "QUARIO_LICENSE": "quario_..." }
    }
  }
}

Leave out the env line to evaluate without a key.

3. Ask for a report. Restart the client, then ask the agent for one:

Render a PDF of these orders with a product column and a total column: Desk, 250, qty 2.

The agent answers with the path of the file it wrote. The file goes to quario-mcp under the system temp directory unless QUARIOOUTDIR says otherwise.

4. Let it read your files (optional). Inline data works everywhere. To let the agent pass a JSON file by dataPath, set QUARIODATAROOT to the directory that holds it. Claude Code sets CLAUDEPROJECTDIR, and the server uses that when QUARIODATAROOT is unset.

Configuration

The server reads its configuration from environment variables. There are no flags and no config file. An empty variable counts as unset.

Shortened. The full README is on GitHub.