Skip to main content
Glama

stack-advisor

An MCP server that recommends tech stacks for your project. Describe what you're building and get a recommended stack with reasoning, tradeoffs, and what each layer should use.

What it does

recommend_stack — describe your project, get 1-3 ranked stack recommendations each with:

  • Full layer breakdown (language, frontend, backend, database, devops, testing)

  • Why this stack fits your use case

  • Tradeoffs to be aware of

  • What it's not good for

list_stacks — see all available stack templates

Related MCP server: project-scaffold

Example prompts

  • "I'm building a SaaS dashboard for small businesses"

  • "What stack should I use for an AI/ML API?"

  • "Best stack for a cross-platform mobile app?"

  • "I need a high-performance Go API for a microservice"

  • "What are the tradeoffs of a serverless edge architecture?"

Add to Claude Desktop

{
  "mcpServers": {
    "stack-advisor": {
      "command": "npx",
      "args": ["-y", "@engineeringmatrixexplorer/stack-advisor"]
    }
  }
}

Add to Claude Code

claude mcp add stack-advisor -- npx -y @engineeringmatrixexplorer/stack-advisor

Available stacks

Stack

Best for

Modern TypeScript Web App

SaaS, dashboards, fullstack apps

Python AI/ML Backend

AI APIs, ML inference, data pipelines

High-Performance Go API

Microservices, high-traffic APIs

React SPA + Node Backend

SPAs, JS-heavy frontends

Enterprise Node.js API

Large teams, structured codebases

Serverless Edge App

Global low-latency, Cloudflare Workers

Mobile App (React Native)

iOS + Android cross-platform

Static Site / Content Site

Blogs, docs, marketing, SEO

Requirements

  • Node.js 18+

Part of the MCP Developer Tools Bundle

This server is also available as part of a bundle with engineering-matrix-explorer and snippet-vault.

License

MIT

Available Tools

2 tools
list_stacksA

List all available stack templates with their tags

Inputs: no named parameters.

recommend_stackA

Describe your project and get 1-3 recommended tech stacks with reasoning, tradeoffs, and what each layer should use.

Inputs: description (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one lists available stack templates, the other provides personalized recommendations. There is no overlap or ambiguity.

    Naming Consistency5/5

    Both tool names follow the same verb_noun pattern in snake_case (list_stacks, recommend_stack), maintaining perfect consistency.

    Tool Count2/5

    With only 2 tools, the surface is too thin for a 'stack advisor' server. Users likely need additional functionality like searching, filtering, or viewing stack details.

    Completeness2/5

    Obvious gaps exist: no way to inspect individual stack templates, search by tags, compare stacks, or manage stacks. The surface is severely limited for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers