project-documenter vs Re:port Flow MCP
project-documenter is a plugin bundle for AI coding tools published by Awesome Copilot Community. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). 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-14. 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
| Marketplace |   Re:port Flow MCP | |
|---|---|---|
| Copilot CLI: github/awesome-copilot | Listed Version: 1.0.0 Forks (GitHub): 5 118 Stars (GitHub): 40 014 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.4.0 Downloads/month (npm): 297 Downloads/week (npm): 99 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
| Fact | project-documenter | Re:port Flow MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 40 014 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 5 118 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.re-port-flow.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 0 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/github/awesome-copilot | github.com/re-port-flow/reportflow-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (26 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
project-documenter
Generate professional project documentation with draw.io architecture diagrams and Word (.docx) output with embedded images. Automatically discovers any project's technology stack and produces Markdown, diagrams, PNG exports, and a formatted Word document.
Re:port Flow MCP
Generate PDF reports from Re:port Flow templates via Claude and other AI agents.
How to run each
project-documenter
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Re:port Flow MCP As a remote MCP server
claude mcp add --transport http reportflow-mcp https://mcp.re-port-flow.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Re:port Flow MCP has a remote endpoint we 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 project-documenter publish no settings it asks for, so we do not compare settings.
What it can do: project-documenter · What it can do: Re:port Flow MCP · Compare two other plugins
Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. 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.