原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Re:port Flow MCP

作者:re-port-flow版本 1.4.0i★ –i电脑或云端
注册名称io.github.re-port-flow/reportflow-mcp

安装

概览

作者提供的说明(英文原文)

Generate PDF reports from Re:port Flow templates via Claude and other AI agents.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在作者的服务器上运行:你向它提出的内容会经过他们的服务器。
  • 需要你自己填写: REPORTFLOW_CLIENT_ID, REPORTFLOW_AUTH_URL, REPORTFLOW_API_BASE_URL, REPORTFLOW_TOKEN_STORE

你需要

  • 在云端运行无需安装任何东西,通过互联网连接
  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude:

  1. 打开 Settings → Connectors
  2. 点击 Add custom connector
  3. 粘贴下面的地址,然后点击 Add
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Add2https://…3
https://mcp.re-port-flow.com/mcp

或者在你的电脑上运行

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "reportflow": {
      "command": "npx",
      "args": [
        "-y",
        "reportflow-mcp"
      ],
      "env": {
        "REPORTFLOW_CLIENT_ID": "your-value",
        "REPORTFLOW_AUTH_URL": "your-value",
        "REPORTFLOW_API_BASE_URL": "your-value",
        "REPORTFLOW_TOKEN_STORE": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add --transport http reportflow https://mcp.re-port-flow.com/mcp

或者在你的电脑上运行

claude mcp add reportflow --env REPORTFLOW_CLIENT_ID=your-value --env REPORTFLOW_AUTH_URL=your-value --env REPORTFLOW_API_BASE_URL=your-value --env REPORTFLOW_TOKEN_STORE=your-value -- npx -y reportflow-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "reportflow": {
      "url": "https://mcp.re-port-flow.com/mcp"
    }
  }
}

或者在你的电脑上运行

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "reportflow": {
      "command": "npx",
      "args": [
        "-y",
        "reportflow-mcp"
      ],
      "env": {
        "REPORTFLOW_CLIENT_ID": "your-value",
        "REPORTFLOW_AUTH_URL": "your-value",
        "REPORTFLOW_API_BASE_URL": "your-value",
        "REPORTFLOW_TOKEN_STORE": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "reportflow": {
      "type": "http",
      "url": "https://mcp.re-port-flow.com/mcp"
    }
  }
}

或者在你的电脑上运行

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "reportflow": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "reportflow-mcp"
      ],
      "env": {
        "REPORTFLOW_CLIENT_ID": "your-value",
        "REPORTFLOW_AUTH_URL": "your-value",
        "REPORTFLOW_API_BASE_URL": "your-value",
        "REPORTFLOW_TOKEN_STORE": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

ChatGPT 只能连接互联网上的服务器:

  1. 打开网页版 ChatGPT → Settings → Connectors (Apps)
  2. 点击 Create 或 Add(部分套餐需要先在 Advanced 中开启 Developer mode)
  3. 粘贴下面的地址,起个名字,然后保存
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Create2https://…3
https://mcp.re-port-flow.com/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • REPORTFLOW_CLIENT_ID env
    Override default OAuth client_id (optional, defaults to the official public client 'reportflow-mcp')
  • REPORTFLOW_AUTH_URL env
    Override default Re:port Flow auth URL (optional, defaults to https://re-port-flow.com/api/v1)
  • REPORTFLOW_API_BASE_URL env
    Override default Re:port Flow Content Service URL (optional, defaults to https://api.re-port-flow.com)
  • REPORTFLOW_TOKEN_STORE env
    Token store backend: 'keychain' (default) or 'file'

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 re-port-flow 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    端点有响应

    尚未检查;我们会轮流检查各个端点

  • … 尚未检查

    使用 OAuth 登录

    尚未检查;我们会轮流检查各个端点

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

与“文档、表格与办公”中的其他服务器比较i

  • 星标数多于此分类中其他 3538 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 3538 个服务器的 24% 更新
  • 基础检查结果等于或优于此分类中其他 3538 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Re:port Flow MCP 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

两种方式都可以:安装在你的电脑上,或者连接云端版本。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(1.4.0)于3个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。

有什么可以替代它?

同一分类中有:Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Agent-Native Calendar

作者:BuilderIO

Agent-Native Google Calendar - manage events, sync, and public booking

在云端运行★ 7,620MIT2个月前更新
安装

Excel MCP Server

作者:haris-musa

Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.

在你的电脑上运行★ 4,276MIT7天前更新
安装

MCP Server for Excel

作者:sbroenne

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

在你的电脑上运行★ 847MIT4天前更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Re:port Flow MCP

Official display name: Re:port Flow MCP. Package and implementation identifier: `reportflow-mcp`. Legacy search aliases: ReportFlow MCP Server and ReportFlow.

Overview

An MCP (Model Context Protocol) server that turns your Re:port Flow templates into PDF reports — invoices, contracts, statements, anything you've designed — straight from Claude or any other MCP-compatible AI agent.

Features

  • Generate PDFs from natural-language requests like *"create an invoice for Acme Corp totalling $300"*
  • Expose your Re:port Flow designs and their parameter schemas directly to the AI as MCP Resources
  • Bulk-generate many PDFs and download them as a single ZIP
  • Save outputs to whichever workspace folder the user is currently in (Claude Desktop / Claude Code / Cursor / VS Code all supported)

Agent Skill

Agents that should follow a procedure (not just read the protocol) use skills/re-port-flow/SKILL.md. Copy that directory into Claude Code / Codex .agents/skills or a Cursor project skill folder. PDF generation always goes to https://mcp.re-port-flow.com/mcp. The Hugging Face Space MCP (org card) is gallery-only — add it from the Space MCP badge → Add to MCP tools, not as a substitute for the product endpoint.

Setup

Re:port Flow MCP runs in two ways — pick whichever matches your client.

Remote server (claude.ai / web clients) — Streamable HTTP

Add Re:port Flow as a custom connector pointing at the hosted endpoint:

https://mcp.re-port-flow.com/mcp

In Claude (claude.ai) go to Settings → Connectors → Add custom connector and paste the URL above. Authentication is handled in-app via OAuth (see Authentication) — nothing to install locally.

Local server (Claude Desktop / Claude Code / Cursor) — stdio via npx

Add the following to your config file (.mcp.json, claude_desktop_config.json, ~/.cursor/mcp.json, etc.):

{

"mcpServers": { "reportflow": { "command": "npx", "args": ["-y", "reportflow-mcp"] } } }

That's the whole setup. No env vars, no API keys, no secrets to manage.

VS Code (MCP-enabled builds)

Same JSON in .vscode/mcp.json.

Requirements
  • Remote: an MCP client that supports custom HTTP connectors (e.g. claude.ai). No local install.
  • Local (stdio): Node.js 22.23.4 or later in the 22.x line (engines: ^22.23.4) and a browser available during the first login. Install a patched Node.js separately; npx downloads the MCP package. The minimum patch requirement includes the 2026-10-21 Node.js security fixes.
  • A Re:port Flow account (either way).
Supported protocol revisions

Both transports (stdio / Streamable HTTP) serve two MCP protocol generations from a single endpoint:

  • `2026-07-28` (current) — stateless per-request protocol. Modern clients discover it via server/discover; no session header, requests carry their protocol version in _meta.
  • 2025-era revisions (2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07) — classic initialize handshake, kept for backwards compatibility with existing clients (Claude Desktop, claude.ai custom connectors, Cursor, ChatGPT, n8n, …).

Version selection is automatic on both transports: modern clients probe with server/discover, legacy clients keep sending initialize — no configuration is required on either side, and existing connections keep working unchanged.

Either handshake also returns MCP instructions: a short brief telling the connected AI what Re:port Flow does and how to reach a first PDF (gallery search → copy → parameters → generate), so it can offer to create a document right after you connect instead of waiting to be asked. How closely a client follows those instructions is up to that client.

A2A (Agent2Agent)

The remote server also speaks A2A v1.0 over the JSON-RPC binding:

  • Agent Card: https://mcp.re-port-flow.com/.well-known/agent-card.json
  • Endpoint: POST https://mcp.re-port-flow.com/a2a (SendMessage)

Each A2A skill is one of the MCP tools above (the skill id is the tool name). Send a message with a data part {"skill": " ", "arguments": {...}}; the arguments follow that tool's input schema, and the call runs through the same authorization and workspace permissions as MCP. Authorize with the same OAuth flow (the MCP access token works as-is). Streaming, push notifications and task retrieval are not supported: every SendMessage returns a finished task.

Authentication

Remote (claude.ai)

When you add the connector, Claude runs the OAuth flow for you: Sign in → pick a workspace → consent. Tokens are held by the client — there's no local keychain or browser step to manage.

Local (stdio)

After reloading the MCP client, ask the AI:

Authenticate with Re:port Flow

A browser window opens. Sign in → pick a workspace → consent, and you're done. Tokens are stored in your OS keychain (macOS Keychain / Windows Credential Manager / Linux libsecret), with a chmod-0600 file fallback, and are refreshed automatically.

Usage examples

Each example below is a prompt you can paste as-is; the AI picks the right tools.

1. Generate a single PDF (list → schema → generate)

Using the invoice template, create a PDF for Acme Corp totalling $330.

The AI lists designs with list_templates, fetches the parameter schema with get_design_parameters, fills in the values, and calls generate_pdf_sync.

  • Remote: returns fileUrl — the output-history page of the Re:port Flow web app (sign-in required). It is not a direct file download link.
  • Synchronous generation times out after 60 seconds (the API returns 504); use generate_pdfs_async for anything that may take longer.
  • Local: also saves the file and returns its absolute path.
2. Batch-generate many PDFs

From the statement template, generate one PDF per customer

(Acme $100, Globex $250, Initech $80) and give them to me together.

  • Local (stdio): generate_pdfs_sync writes a single ZIP to your workspace.
  • Remote: generate_pdfs_async runs the batch and returns a request id plus the output-history page URL (url). get_generation_status tells you when the batch has finished or failed.
3. Async generate, then download (local)

Kick off the contract PDF in the background, then download it once it's ready.

The AI calls generate_pdf_async (returns a requestId immediately), checks progress with get_generation_status, then calls download_file to save the finished PDF. The batch equivalent is generate_pdfs_async → download_zip. If a download is attempted while the file is still being generated, the tool reports FILE_NOT_READY with the number of seconds to wait instead of failing. These download tools are stdio-only; on the remote server the sync/async tools return the output-history page URL instead.

requestId, fileId and designId are short alphanumeric strings (for example 0eUDdgAjNXrrItA2), not UUIDs.

Tip — natural-language params: on a Sampling-capable client you can ask

*"draft the params for a $1,000 invoice to A社"* and the AI will call

suggest_params to turn the brief into a valid params object before

generating.

4. Start from zero templates (gallery → copy → generate)

I don't have any templates yet — create an invoice PDF for Acme Corp.

When list_templates is empty, the AI searches the public template gallery with search_gallery_templates, shows you the candidates, copies your pick into your workspace with copy_gallery_template, and then proceeds with the normal flow (get_design_parameters → generate_pdf_sync). The copy always lands in the workspace you selected on the OAuth consent screen — the AI cannot target any other workspace.

If the search finds nothing, the result carries a templateSite link to the template gallery site, where you can browse the designs. Share the page URL of the one you like (/templates/{slug}) and the AI copies it by that slug.

Slash commands
CommandPurpose
/generate_pdfStep-by-step recipe for a single PDF
/generate_pdfsRecipe for batch PDF generation
/reportflow_helpQuick feature tour
Where files are saved (local mode)

Output location is resolved in this order:

  1. Explicit instruction from the user (e.g. *"save to my Desktop"*)
  2. The currently-open workspace root (Claude Code / Cursor / VS Code)
  3. The OS temp directory as fallback

Build your own agent

The setup above assumes an MCP client that manages its own connection and login. If you are writing the agent yourself — Hugging Face Agents, a custom tool loop, or raw HTTP — the hosted endpoint is open to you directly:

https://mcp.re-port-flow.com/mcp
  • [agents.md](./agents.md) — the agent-facing guide: transport details, the ten HTTP tools, the OAuth flow, model selection, and the rules an agent has to follow (never invent business data; copy_gallery_template is not idempotent; passthrough values end up in the PDF's metadata).
  • [examples/](./examples/) — runnable Python, JavaScript and curl clients, plus a script that walks the OAuth flow and prints an access token.

initialize and tools/list work without credentials, so you can discover the toolset before wiring up authentication. Every tools/call needs a Bearer token.

Hugging Face

Re:port Flow is on the Hub at [huggingface.co/reportflow](https://huggingface.co/reportflow). The Hugging Face SDKs have no MCP OAuth flow of their own, so fetch a token once with examples/oauth/get-token.sh and inject it as an Authorization header — see examples/python/hf_mcp_client.py and examples/javascript/hf-mcp-client.mjs.

Reference

Tools (called by the AI)
ToolPurpose
authenticateFirst-time / re-authentication
list_templatesList available designs
get_design_parametersFetch the parameter schema for a design
generate_pdf_sync / _asyncGenerate one PDF (sync returns path; async returns request ID)
generate_pdfs_sync / _asyncGenerate many PDFs (returns a ZIP)
get_generation_statusCheck an async request (requestId): processing / completed / failed, with the failure code and message
download_file / download_zipDownload artifacts produced by async tools (stdio only). Returns FILE_NOT_READY + seconds to wait while the file is still being generated
suggest_paramsTranslate a natural-language brief into a params JSON via MCP Sampling (requires a Sampling-capable client)
search / fetchChatGPT connector convention tools (single string argument), closed-world (openWorldHint: false) — they only read your own workspace's internal template catalog, never the web. search resolves templates by name; fetch returns a template's parameter schema by id. Thin wrappers over list_templates / get_design_parameters so ChatGPT (incl. Plus/Pro without Developer Mode) can discover and inspect templates.
search_gallery_templatesSearch the public template gallery (no auth needed) by keyword/category. Returns candidate templates that are *not yet* in your workspace — their slug cannot be used for PDF generation until copied.

| get_gallery_template | Fetch full details of one public gallery template by slug (no au

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx