tf-diagram vs DrillFlow
tf-diagram is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑21.
tf-diagram is a plugin bundle for AI coding tools published by Miguel Alarcon. No marketplace we read lists it any more. DrillFlow is an MCP server published by drillflow.de. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-21. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  DrillFlow | |
|---|---|---|
| Community marketplace anllacarpro/tf-diagram-skill | Removed on 2026-10-21 Version: 0.3.2 Forks (GitHub): 0 Stars (GitHub): 6 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.89 Downloads/month (npm): 2 193 Downloads/week (npm): 508 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.0.89 Downloads/month (npm): 2 193 Downloads/week (npm): 508 Forks (GitHub): 0 Stars (GitHub): 0 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 | tf-diagramno longer listed · | DrillFlow |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 6 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (drillflow-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/anllacarpro/tf-diagram-skill | github.com/capydev42/drillflow-mcp |
| Changes in the last 7 days (differs) | 4 | 16 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of tf-diagram
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Draw cloud architecture diagrams with official AWS, Azure and GCP icons from a prompt or Terraform.
-
Generate and edit AWS, Azure, GCP and Kubernetes architecture diagrams as editable draw.io files.
-
Generate cloud architecture diagrams, flowcharts, and sequence diagrams.
-
Seamlessly create diagrams using the Python diagrams package DSL. This server allows you to generate AWS diagrams, sequence diagrams, flow diagrams, and class diagrams using…
-
Create and update live animated architecture diagrams on CloudArch from a prompt or script.
-
drawarch io.github.Ajey95/drawarch
Create editable Draw.io architecture diagrams from prompts and reference images.
What each says it does
tf-diagram
Generate professional architecture diagrams (.drawio + PNG) from Terraform projects with official cloud icons.
DrillFlow
Publish drill-down diagrams from an agent; every Mermaid subgraph becomes a level you enter.
How to run each
tf-diagram
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
DrillFlow As a local MCP server: npm package
claude mcp add --env "DRILLFLOW_TOKEN=<YOUR_DRILLFLOW_TOKEN>" --transport stdio drillflow -- npx -y drillflow-mcpRequires: DRILLFLOW_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
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 tf-diagram publish no settings it asks for, so we do not compare settings.
What it can do: tf-diagram · What it can do: DrillFlow · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.