Ext Ops Panel
Open dashboard
Comparison

DocuQueue MCP vs Re:port Flow MCP

DocuQueue MCP is an MCP server published by dvcoolarun. Marketplaces we read that list it: 1 (Official MCP Registry). Re:port Flow MCP is an MCP server published by re-port-flow. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceDocuQueue MCPRe:port Flow MCP
Official MCP Registry Listed
Version: 0.1.5
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.4.0
Downloads/month (npm): 263
Downloads/week (npm): 21
Forks (GitHub): 1
Stars (GitHub): 1
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

DocuQueue MCP vs Re:port Flow MCP
FactDocuQueue MCPRe:port Flow MCP
Marketplaces that list it11
Stars (GitHub)11
Forks (GitHub) (differs)0 (worse)1 (better)
Last release (differs)2026-10-26Not published
Where it runs (differs)Remote server (docuqueue.com/mcp/v1)Remote server (mcp.re-port-flow.com/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/docuqueue/docuqueue-mcpgithub.com/re-port-flow/reportflow-mcp
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 400 (23 h ago)Answered with HTTP 404 (41 h ago)

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

DocuQueue MCP

In its own words, on Official MCP Registry:

MCP server for PDF generation, form filling, batch invoices and contracts. MIT, free tier, hosted.

Re:port Flow MCP

In its own words, on Official MCP Registry:

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

How to run each

DocuQueue MCP As a remote MCP server

Claude Code
claude mcp add --transport http docuqueue-mcp https://docuqueue.com/mcp/v1

Re:port Flow MCP As a remote MCP server

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

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Neither endpoint responded at the last daily check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of DocuQueue MCP publish no settings it asks for, so we do not compare settings.

What it can do: DocuQueue MCP · What it can do: Re:port Flow MCP · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built