Ext Ops Panel
Open dashboard
Comparison

io.github.HeshamFS/mcp-tool-factory vs io.github.silex-tec/silex

io.github.HeshamFS/mcp-tool-factory is an MCP server published by HeshamFS. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.silex-tec/silex is an MCP server published by silex-tec. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
Marketplaceio.github.HeshamFS/mcp-tool-factoryio.github.silex-tec/silex
Official MCP Registry Listed
Version: 0.1.0
Downloads/month (npm): 166
Downloads/week (npm): 53
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.11.38
Downloads/month (PyPI): 1 092
Downloads/week (PyPI): 17
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

io.github.HeshamFS/mcp-tool-factory vs io.github.silex-tec/silex
Factio.github.HeshamFS/mcp-tool-factoryio.github.silex-tec/silex
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@heshamfsalama/mcp-tool-factory)On your machine (silex-archaeology)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)4, secrets among them: 4Not published
LicenceNot statedNot stated
Repository (differs)github.com/heshamfs/mcp-tool-factory-tsgithub.com/silex-tec/silex
Changes in the last 7 days00
First seen2026-10-112026-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

io.github.HeshamFS/mcp-tool-factory

In its own words, on Official MCP Registry:

Generate MCP servers from natural language, OpenAPI specs, or database schemas.

io.github.silex-tec/silex

In its own words, on Official MCP Registry:

Local-first MCP server that reconstructs architecture, workflows and business rules from your code.

How to run each

io.github.HeshamFS/mcp-tool-factory As a local MCP server: npm package

Claude Code
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --env "CLAUDE_CODE_OAUTH_TOKEN=<YOUR_CLAUDE_CODE_OAUTH_TOKEN>" --env "GOOGLE_API_KEY=<YOUR_GOOGLE_API_KEY>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio mcp-tool-factory -- npx -y @heshamfsalama/mcp-tool-factory

Requires: ANTHROPIC_API_KEY (secret), CLAUDE_CODE_OAUTH_TOKEN (secret), GOOGLE_API_KEY (secret), OPENAI_API_KEY (secret)

io.github.silex-tec/silex As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio silex -- uvx silex-archaeology

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 io.github.silex-tec/silex publish no settings it asks for, so we do not compare settings.

What it can do: io.github.HeshamFS/mcp-tool-factory · What it can do: io.github.silex-tec/silex · 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