What can you do with this server?

This server scans a project directory to detect its tech stack and can either generate a visual HTML report or return the findings as structured JSON. * Generate a visual HTML report (generate_tech_stack): Produces a self-contained TECH_STACK.html file featuring a stat row (total tools, categories, AI backends, data stores), a layered architecture diagram, a horizontal bar chart, and colour-coded tool cards. Optionally auto-opens in your default browser. Output path and project directory are configurable. * Return a structured JSON summary (list_tech_stack): Scans the project and returns the tech stack as structured JSON without writing any file — ideal for programmatic or downstream use. * Detects a wide range of technologies: Languages (Python, Go, Rust, TypeScript, Java, PHP...), frameworks (FastAPI, Django, Express, Next.js...), databases (PostgreSQL, Redis, MongoDB, SQLite...), AI/ML SDKs, testing, observability, security, and infrastructure (Docker, Kubernetes, CI/CD, GitHub Actions, GitLab CI). * Zero configuration required: All inputs are optional and default to the current working directory. Works with Claude Desktop, VS Code, Cursor, Zed, and Continue.

Which integrations are available for this server?

Provides a GitHub Copilot Extension that allows users to generate tech stack reports by invoking /generate-tech-stack in Copilot Chat.

Generate Tech Stack

by askuma

Overview Schema Related Servers Score Discussions

Python

Local

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:

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
Guided tour	Spotlight walkthrough of every section, shown automatically the first time a report is opened; replay anytime with the `?` button
Theme toggle	Sun/moon button next to the tour button switches between dark and light mode

Related MCP server: mcp-repo-graph

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, writes TECH_STACK.html, opens in browser
list_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 SDKs	Blue	OpenAI, Anthropic, LangChain, GuardrailsAI, NVIDIA NeMo, Presidio
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 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.

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/askuma/generate-tech-stack'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

Generate Tech Stack

generate-tech-stack

What it produces

Repository layout

Usage

pip (CLI + MCP server)

Claude Code

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

GitHub Copilot Extension

Command line (standalone)

What gets detected

Detected categories

Design

See also

Maintenance

Resources

Tools

Related MCP Servers

lore-mcp

mcp-repo-graph

Code Expert MCP Server

Axon Pro

Related MCP Connectors

Latest Blog Posts

MCP directory API