Skip to content
External endpointresponds

ReportFlow

Generate PDF reports from ReportFlow templates via Claude and other AI agents.

Endpoint URL
https://mcp.re-port-flow.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:04 AM UTC
Check
MCP initialize · 8s limit
Latency
483 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.re-port-flow/reportflow-mcp

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
reportflow-mcp
Version
1.4.0
Capability keys
tools, prompts, resources
Tool names
get_design_parameters, list_templates, generate_pdf_sync, generate_pdfs_async, suggest_params, search, fetch, search_gallery_templates, get_gallery_template, copy_gallery_template
Instructions excerpt

You are connected to Re:port Flow, a service that generates business PDF documents — invoices, quotations, delivery notes and other business forms — from reusable templates. When the user has just connected and has not asked for anything yet, do not wait in silence: proactively offer to create their first document. For example: "Re:port Flow is connected. Want to try it? Just say 'Create an invoice with Re:port Flow.'" Fastest path to a first PDF: list_templates -> only if it holds nothing that fits: search_gallery_templates -> copy_gallery_template -> then get_design_parameters -> generate_pdf_sync - Start at list_templates: a template the workspace already owns is the better choice, and reaching for the gallery instead would create a duplicate of something it already has. - list_templates coming back with no designs is the normal starting state of a new workspace, not an error — bring a template in from the public gallery with search_gallery_templates and copy_gallery_templa

Reported Aug 17, 2026, 05:04 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 1,118ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 1,046ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 407ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 483ms