twitter-reader vs io.github.jbechtel-97/dealflowpro
twitter-reader is a plugin bundle for AI coding tools published by daymade. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.jbechtel-97/dealflowpro is an MCP server published by jbechtel-97. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-20. 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 |  twitter-reader |  io.github.jbechtel-97/dealflowpro |
|---|---|---|
| Community marketplace daymade/claude-code-skills | Listed Version: 1.4.0 Forks (GitHub): 228 Stars (GitHub): 1 480 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.2.9 Downloads/month (npm): 630 Downloads/week (npm): 377 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.2.9 Downloads/month (npm): 630 Downloads/week (npm): 377 Forks (GitHub): 0 Stars (GitHub): 4 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 | twitter-reader | io.github.jbechtel-97/dealflowpro |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 1 480 (better) | 4 (worse) |
| Forks (GitHub) (differs) | 228 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (dealflowpro-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/daymade/claude-code-skills | github.com/jbechtel-97/dealflowpro-mcp-server |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
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
twitter-reader
Fetch Twitter/X post content including long-form Articles with full images and metadata. Use when Claude needs to retrieve tweet/article content, author info, engagement metrics (likes, retweets, bookmarks), and embedded media. Supports individual posts and X Articles (long-form content). Automatically downloads all images to local attachments folder and generates complete Markdown with proper image references. Preferred over Jina for X Articles with images.
io.github.jbechtel-97/dealflowpro
Multifamily real estate deal analysis — cap rate, DSCR, IRR, DFP Score, max offer price
How to run each
twitter-reader As a Claude Code plugin
/plugin marketplace add daymade/claude-code-skills
/plugin install twitter-reader@daymade-skillsio.github.jbechtel-97/dealflowpro As a local MCP server: npm package
claude mcp add --env "DFP_API_KEY=<YOUR_DFP_API_KEY>" --transport stdio dealflowpro -- npx -y dealflowpro-mcpRequires: DFP_API_KEY (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 twitter-reader publish no settings it asks for, so we do not compare settings.
What it can do: twitter-reader · What it can do: io.github.jbechtel-97/dealflowpro · 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.