Generate Tech Stack
Visual tech-stack inventory of any codebase: languages, frameworks, databases, AI SDKs, infra.
README
generate-tech-stack
<!-- mcp-name: io.github.askuma/generate-tech-stack -->
Scan any project and generate a visual TECH_STACK.html page — dark-mode, 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.

What it produces
Every generated page contains:
| Section | Description |
|---|---|
| Stat row | Total tools · Categories · AI Backends · Data Stores |
| Architecture diagram | Layered flow diagram (Consumer → API → AI/NLP → Data/Obs/Frontend) |
| Bar chart | Horizontal bars per category, colour-matched |
| Tool cards | One card per category; each tool shows a dot, name, description, and badge |
| Badge legend | Explains pip, dep, optional, core, deploy, ci, etc. |
| Footer | Project name · tool count · generation date |
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)
pip install generate-tech-stack-mcp
generate-tech-stack . TECH_STACK.html # CLI: scan and write the report
generate-tech-stack-mcp # stdio MCP server
With pip installed, any MCP host config reduces to:
{
"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)
pip install mcp
Add to your host's MCP config (replace the path with your actual home directory):
{
"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, writesTECH_STACK.html, opens in browserlist_tech_stack— returns a JSON summary, no file written
GitHub Copilot Extension
cd copilot
npm install
npm start # listens on port 3000
ngrok 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)
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 file | Detected tools |
|---|---|
requirements.txt / pyproject.toml |
Python packages (web, DB, AI, testing, observability, security…) |
package.json |
Node / npm packages (frameworks, frontend, DB drivers, tooling) |
go.mod |
Go language |
Cargo.toml |
Rust language |
pom.xml / build.gradle |
Java / Kotlin |
Gemfile |
Ruby |
composer.json |
PHP |
**/*.py source |
Optional/dynamic SDKs via importlib.find_spec() patterns |
docker-compose.yml / .env |
PostgreSQL, Redis, MongoDB, SQLite connection strings |
Dockerfile |
Docker |
docker-compose.yml |
Docker Compose |
.github/workflows/ |
GitHub Actions |
.gitlab-ci.yml |
GitLab CI |
alembic.ini |
Alembic migrations |
nginx.conf / Caddyfile |
Reverse proxy |
tsconfig.json / src/**/*.ts |
TypeScript |
Detected categories
| Category | Colour | Examples |
|---|---|---|
| Language & Runtime | Green | Python, Go, Rust, TypeScript |
| Web / API Framework | Purple | FastAPI, Express, Django, Next.js |
| Database / Storage | Green | SQLAlchemy, Prisma, Redis, ChromaDB |
| AI Guardrail SDKs | Blue | GuardrailsAI, NVIDIA NeMo, Presidio, Lakera |
| NLP / ML | Teal | spaCy, Transformers, Sentence Transformers |
| Observability | Teal | Prometheus, OpenTelemetry, Sentry, Loguru |
| Testing | Yellow | pytest, Jest, Cypress, Playwright |
| Security / Auth | Rose | PyJWT, bcrypt, Authlib, Helmet |
| Infrastructure / Deploy | Orange | Docker, Kubernetes, Celery, Boto3 |
| Frontend / Dashboard | Gray | React, Vue, Tailwind, Recharts |
| Messaging / Comms | Blue | Kafka, RabbitMQ, Socket.io |
| Dev Tools | Gray | ESLint, Prettier, Vite, TypeScript |
Design
Dark-mode only. Fonts: IBM Plex Sans (body) + JetBrains Mono (code/badges), loaded from Google Fonts. No JavaScript — pure 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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.