Generate Tech Stack

io.github.askumaPublished by GitHub account askumav0.2.2Updated Oct 24, 2026

Visual tech-stack inventory of any codebase: languages, frameworks, databases, AI SDKs, infra.

The publisher's own server: Tech.eu Funding Explorer

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

Scans a local codebase and generates a visual TECH_STACK.html report of languages, frameworks, databases, AI SDKs, and infrastructure.

What you can do
Exposes two MCP tools: generate_tech_stack scans a project, writes a self-contained TECH_STACK.html report, and opens it in the browser; list_tech_stack returns a JSON summary without writing a file. Detection covers dependency and config files such as requirements.txt, pyproject.toml, package.json, go.mod, Cargo.toml, Dockerfile, docker-compose.yml, and CI workflow files, and groups findings into categories like language, web framework, database, AI SDKs, observability, testing, security, and infrastructure. The report includes a stat row, architecture diagram, bar chart, tool cards, badge legend, and a guided tour.
When to use it
Useful when you want a quick visual inventory of a project's stack for onboarding, documentation, or review, or when an assistant should summarize a repository's dependencies and tooling without reading every manifest by hand.
Requirements
Runs locally over stdio. Install the PyPI package generate-tech-stack-mcp (or the mcp package for the server script); Python 3.8+ is required, and the scanner itself has no third-party dependencies. No accounts, API keys, or environment variables are declared.
Before you install
The generate_tech_stack tool writes a TECH_STACK.html file into the scanned project directory and opens it in the browser, so point it at directories you are comfortable modifying. The generated page loads fonts from Google Fonts, which contacts a third party when opened; the report is otherwise self-contained.

Installation

In SourceWeft

  1. Open Generate Tech Stack in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

generate-tech-stack

Scan any project and generate a visual TECH_STACK.html page — light/dark theme, auto-adapting, zero config.

Works as a Claude Code skill, MCP server, or GitHub Copilot Extension.

Live demo → — generated from fastapi/full-stack-fastapi-template, unmodified.

[Running generate-tech-stack against fastapi/full-stack-fastapi-template, from pip install to the generated page]

(real CLI output, unscripted — static screenshot if you'd rather not autoplay)


What it produces

Every generated page contains:

SectionDescription
Stat rowTotal tools · Categories · AI Backends · Data Stores
Architecture diagramLayered flow diagram (Consumer → API → AI/NLP → Data/Obs/Frontend)
Bar chartHorizontal bars per category, colour-matched
Tool cardsOne card per category; each tool shows a dot, name, description, and badge
Badge legendExplains pip, dep, optional, core, deploy, ci, etc.
FooterProject name · tool count · generation date
Guided tourSpotlight walkthrough of every section, shown automatically the first time a report is opened; replay anytime with the ? button
Theme toggleSun/moon button next to the tour button switches between dark and light mode

Repository layout

~/.claude/skills/generate-tech-stack/├── SKILL.md                  ← Claude Code skill definition├── INSTALL.md                ← detailed per-platform installation guide├── README.md                 ← this file├── scripts/│   └── analyze.py            ← core scanner + HTML renderer (no dependencies)├── mcp/│   ├── server.py             ← MCP stdio server (pip install mcp)│   └── requirements.txt└── copilot/    ├── index.js              ← GitHub Copilot Extension (Express)    ├── package.json    └── openai_function.json  ← OpenAI / Antigravity function definition

Usage

pip (CLI + MCP server)

bash
pip install generate-tech-stack-mcp
generate-tech-stack . TECH_STACK.html    # CLI: scan and write the reportgenerate-tech-stack-mcp                   # stdio MCP server

With pip installed, any MCP host config reduces to:

json
{  "mcpServers": {    "generate-tech-stack": { "command": "generate-tech-stack-mcp" }  }}

Claude Code

/generate-tech-stack

Run it from any project directory. The skill calls scripts/analyze.py and opens the result in your browser.

MCP (Claude Desktop, VS Code, Cursor, Zed, Windsurf, Continue)

bash
pip install mcp

Add to your host's MCP config (replace the path with your actual home directory):

json
{  "mcpServers": {    "generate-tech-stack": {      "command": "python3",      "args": ["/home/<you>/.claude/skills/generate-tech-stack/mcp/server.py"]    }  }}

Then ask: generate my tech stack or /generate-tech-stack.

MCP tools exposed:

  • generate_tech_stack — scans a project, writes TECH_STACK.html, opens in browser
  • list_tech_stack — returns a JSON summary, no file written

GitHub Copilot Extension

bash
cd copilotnpm installnpm start        # listens on port 3000ngrok http 3000  # expose for GitHub to reach

Register a GitHub App with Copilot Extension enabled, set the Agent URL to https://your-url/agent, and install it on your account. Then in Copilot Chat:

@generate-tech-stack /generate-tech-stack@generate-tech-stack /generate-tech-stack /path/to/project

Command line (standalone)

bash
python3 ~/.claude/skills/generate-tech-stack/scripts/analyze.py /path/to/project# output: /path/to/project/TECH_STACK.html
# custom output path:python3 scripts/analyze.py . ~/Desktop/TECH_STACK.html

analyze.py has no third-party dependencies — just Python 3.8+.


What gets detected

Source fileDetected tools
requirements.txt / pyproject.tomlPython packages (web, DB, AI, testing, observability, security…)
package.jsonNode / npm packages (frameworks, frontend, DB drivers, tooling)
go.modGo language
Cargo.tomlRust language
pom.xml / build.gradleJava / Kotlin
GemfileRuby
composer.jsonPHP
**/*.py sourceOptional/dynamic SDKs via importlib.find_spec() patterns
docker-compose.yml / .envPostgreSQL, Redis, MongoDB, SQLite connection strings
DockerfileDocker
docker-compose.ymlDocker Compose
.github/workflows/GitHub Actions
.gitlab-ci.ymlGitLab CI
alembic.iniAlembic migrations
nginx.conf / CaddyfileReverse proxy
tsconfig.json / src/**/*.tsTypeScript

Detected categories

CategoryColourExamples
Language & RuntimeGreenPython, Go, Rust, TypeScript
Web / API FrameworkPurpleFastAPI, Express, Django, Next.js
Database / StorageGreenSQLAlchemy, Prisma, Redis, ChromaDB
AI SDKsBlueOpenAI, Anthropic, LangChain, GuardrailsAI, NVIDIA NeMo, Presidio
NLP / MLTealspaCy, Transformers, Sentence Transformers
ObservabilityTealPrometheus, OpenTelemetry, Sentry, Loguru
TestingYellowpytest, Jest, Cypress, Playwright
Security / AuthRosePyJWT, bcrypt, Authlib, Helmet
Infrastructure / DeployOrangeDocker, Kubernetes, Celery, Boto3
Frontend / DashboardGrayReact, Vue, Tailwind, Recharts
Messaging / CommsBlueKafka, RabbitMQ, Socket.io
Dev ToolsGrayESLint, Prettier, Vite, TypeScript

Design

Dark by default with a light-mode toggle (top-right corner, no persistence — resets to dark on reload). Fonts: IBM Plex Sans (body) + JetBrains Mono (code/badges), loaded from Google Fonts. Vanilla JS powers the guided tour and theme toggle only — everything else is plain HTML + CSS. Self-contained single file, opens in any browser offline.


See also

  • INSTALL.md — per-platform setup instructions
  • SKILL.md — Claude Code skill specification

Source: README.md at commit e4a395a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Tech integrations