Reportflow Mcp

What is Reportflow Mcp?

Reportflow Mcp is a Model Context Protocol server for generating business documents (PDFs) from natural-language requests. It integrates with ReportFlow’s no-code template designer and marketplace, exposing designs, parameter schemas, and PDF generation as MCP tools, resources, and prompts. It is aimed at business users who need document automation without a development environment.

How to use Reportflow Mcp?

Two modes are supported. Remote (recommended): configure your MCP client with an HTTP endpoint at https://mcp.re-port-flow.com/mcp – no Node.js installation required. Local (stdio): set the MCP server command to npx -y reportflow-mcp (Node.js 18+ needed). On first use, authenticate via OAuth 2.0 (browser consent flow); for local mode, ask the AI to “authenticate with ReportFlow”. After setup, the AI can invoke tools like generate_pdf_sync and list_templates directly.

Key features of Reportflow Mcp

• Remote-ready, setup-free hosted endpoint (no Node.js required)
• No-code template design via Konva-based browser GUI
• Free template marketplace for invoices, quotes, receipts, and more
• OAuth 2.0 + PKCE + Dynamic Client Registration (no API key exposed)
• Bulk PDF generation with single ZIP download
• Tool annotations (title, readOnlyHint, destructiveHint) for MCP-aware clients

Use cases of Reportflow Mcp

• Generate an invoice or quote from a natural-language description (e.g., "create an invoice for Acme Corp totalling $330")
• Produce receipts, delivery slips, or reports using ready-made templates from the gallery
• Bulk-generate many PDFs and download them as a single ZIP archive
• Allow business users without a local dev setup to start generating documents immediately

FAQ from Reportflow Mcp

How does Reportflow Mcp differ from other document-generation MCP servers?

Reportflow Mcp is remote-ready (no Node.js needed), uses a no-code browser-based template editor with a free marketplace, and authenticates via OAuth 2.0 + PKCE + Dynamic Client Registration—no API key is shared with the AI client.

What are the runtime requirements?

Remote mode: An MCP-capable AI client (e.g., Claude.ai, Claude Desktop, Cursor, VS Code) and a ReportFlow account. Local mode: Node.js 18+, a browser for first-run OAuth consent, and a ReportFlow account.

How does authentication work?

On first connection, a browser tab opens for OAuth consent (workspace selection and approval). Tokens are managed server-side (remote) or stored in the OS keychain/local file (local). No manual API key configuration is needed.

What templates are available?

A free template gallery at https://templates.re-port-flow.com covers invoices, quotes, receipts, delivery slips, reports, and more. Users can also design custom templates in the browser GUI.

What transport protocols and authentication methods are supported?

Transport: HTTP (remote) and stdio (local). Auth: OAuth 2.0 Authorization Code + PKCE with Dynamic Client Registration.