lp.re-port-flow.com

Re:port Flow is a cloud service for creating document templates and generating PDFs such as invoices, reports, and application forms. It provides a visual template editor, API-based PDF generation, and AI-client integration via MCP.

3 integrations · MCP · REST · CLI

Re:port Flow exposes a REST API at `api.re-port-flow.com/v1` for PDF/document generation plus an MCP server at `mcp.re-port-flow.com/mcp`; the API supports `appkey` header auth or OAuth 2.0 Bearer tokens, and the MCP server uses OAuth 2.0 with dynamic client registration. It also ships an npm-distributed local MCP executable (`reportflow-mcp`) run via `npx`.

discovered 2mo ago

MCP servers1

Report Flow MCPdetectedstreamable-http

REST · OpenAPI1

Report Flow REST APIdiscoveredrest

CLI1

reportflow-mcpdiscoverednpx

Credentials

Report Flow application keyapi_keyGet key ↗

Sign in to Report Flow, open your workspace, then go to ワークスペース設定 / Workspace Settings → API連携 and copy the アプリケーションキー (ak_...). If you do not have an account yet, register at Sign up. The docs say each workspace has one application key and you can rotate it from the same API連携 screen.

Report Flow OAuth clientoauth2Set up OAuth ↗

For OAuth API access, first sign in to Report Flow. The docs state Report Flow supports OAuth 2.0 / OpenID Connect with Authorization Code + PKCE for user-authorized apps and Client Credentials for server-to-server apps. Create or register an OAuth client in the Report Flow app/admin flow, then use the issuer metadata at `https://re-port-flow.com/api/v1/.well-known/openid-configuration` to discover the authorization and token endpoints. Public clients use PKCE without a client secret; confidential clients use a client secret and can use client_credentials.

Report Flow MCP OAuthoauth2$ npx -y reportflow-mcp

Acquired by the CLI — running npx -y reportflow-mcp opens the auth flow and stores the credential.

Report Flow OAuthoauth2

MCP 対応 AI クライアント（Claude Desktop / Claude Code / Cursor / VS Code 等）から MCP サーバーに接続すると、OAuth 2.0（Authorization Code + PKCE、動的クライアント登録）により自動的に認可されます。API キーの発行・管理は不要です。認可サーバーは MCP 接続 URL から RFC 9728 / RFC 8414 で解決できます。

conventions · 3/8 published

integrations.json✓https://lp.re-port-flow.com/.well-known/integrations.json
llms.txt✓https://lp.re-port-flow.com/llms.txt
API catalog✗/.well-known/api-catalog
OpenAPI document✗/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json
MCP server card✓https://mcp.re-port-flow.com/mcp
OAuth protected resource✗/.well-known/oauth-protected-resource
Agent card✗/.well-known/agent-card.json
Agent skills✗/.well-known/agent-skills/index.json

Publish these signals → /publishing