Skip to main content
Glama

StackGuide MCP Server

Dynamic context + active engineering workflow for AI coding assistants in Cursor, VS Code, and other MCP clients.

npm version license mcp registry

What It Does

@stackguide/mcp-server helps teams standardize implementation quality with:

  • project-aware rule/context loading

  • code review and health scoring

  • auto-detected setup and stack scaffolding

  • active agent workflow that executes real work (intake, plan, verify, release)

  • adaptive TDD preferences per project (model + token profile)

  • Jira ticket creation from strict MAIN DESCRIPTION templates

  • tracker + VCS + test orchestration for delivery flow

This server is built for real team usage, not just prompt templates.

Related MCP server: TechStack Local MCP Server

What's New In v4.x

  • Added active agent tool (execution-first workflow).

  • init now generates .stackguide/config.json automatically.

  • Added tracker service support for GitHub, GitLab, and Jira.

  • Added VCS service for branch checks, commit parsing, CI status, and PR/MR creation.

  • Added test runner service for structured test/lint/build execution.

  • Updated TDD prompts to use active tool calls instead of large passive markdown payloads.

  • Hardened local persistence:

    • .stackguide artifacts removed from version control

    • repository guard blocks accidental tracking of local artifacts

    • cache and health history include integrity validation and safer writes

Install By IDE

Cursor

  • File (workspace): .cursor/mcp.json

  • File (global): ~/.cursor/mcp.json

{
  "mcpServers": {
    "stackguide": {
      "command": "npx",
      "args": ["-y", "@stackguide/mcp-server@latest"]
    }
  }
}

JetBrains (IntelliJ, WebStorm, PhpStorm, etc.)

  • Open Settings | Tools | AI Assistant | Model Context Protocol (MCP).

  • Click Add and paste JSON config.

  • Recommended: set it as Project-level unless you want global scope.

{
  "mcpServers": {
    "stackguide": {
      "command": "npx",
      "args": ["-y", "@stackguide/mcp-server@latest"]
    }
  }
}

VS Code

  • Requirement: GitHub Copilot Chat with MCP enabled.

  • File (workspace): .vscode/mcp.json

  • VS Code MCP schema uses servers as root key.

{
  "servers": {
    "stackguide": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@stackguide/mcp-server@latest"]
    }
  }
}

Visual Studio (Windows, 2022 17.14+ / 2026+)

  • Enable GitHub Copilot Agent mode.

  • Supported config locations include:

    • %USERPROFILE%\\.mcp.json (global)

    • <solution>\\.mcp.json (repo-scoped)

    • <solution>\\.vs\\mcp.json (solution/user-scoped)

  • Visual Studio MCP schema uses servers as root key.

{
  "servers": {
    "stackguide": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@stackguide/mcp-server@latest"]
    }
  }
}

How To Use (Any IDE)

  1. Restart the IDE after adding the MCP configuration.

  2. Open AI chat in agent/tool mode.

  3. Call setup to detect project context.

  4. Call init action:"full" to scaffold .stackguide/ and defaults.

  5. Use agent actions (intake, create_ticket, plan, verify, release) for delivery flow.

Quick Start

  1. Configure your project:

setup type:"react-typescript" enableAdaptiveTdd:true model:"gpt-5" integrations:["jira","github"] tokenMode:"compact"
init action:"full" model:"gpt-5" tokenMode:"compact" integrations:["jira","github"] mcpSyncTargets:["cursor","root"] applyMcpTemplates:true
  1. Check generated setup:

init action:"status"
agent action:"status"
  1. Run active TDD workflow:

agent action:"intake" ticket:"PROJ-123"
agent action:"create_ticket" mainDescription:"<MAIN DESCRIPTION>" projectKey:"PROJ"
agent action:"plan" brief:"<brief-from-intake>"
agent action:"verify"
agent action:"release" version:"v1.2.0"

Tools (16)

Core

  • setup: configure StackGuide context for project type

  • context: show currently loaded context

  • rules: list/search/get/select rule sets

  • knowledge: list/search/get knowledge files

  • review: analyze files/URLs/project code quality

Utility

  • cursor: browse/import community rules

  • docs: fetch/search/list documentation

  • config: save/load/export/import configurations

  • custom_rule: create/update/delete/list project custom rules

  • help: usage help by topic

Advanced

  • generate: boilerplate generation (component/hook/service/test/api/model/util)

  • health: project health score and recommendations

  • analyze: project intelligence (structure/config/dependency/generate/apply)

Workflow

  • workflow: lazy-load raw workflow assets (agents/skills/hooks/commands)

  • init: scaffold .stackguide with stack-aware defaults

  • agent: active workflow executor (status, intake, create_ticket, plan, verify, release)

Active Workflow Details

agent action:"intake"

  • reads ticket from configured tracker

  • returns normalized brief + gaps

  • proposes branch name convention

  • can optionally create a Jira ticket first (createFromDescription:true)

agent action:"create_ticket"

  • creates Jira issues using strict MAIN DESCRIPTION format

  • uses project defaults from .stackguide/config.json (projectKey, issueType)

  • derives summary from first line of MAIN DESCRIPTION when omitted

agent action:"plan"

  • inspects conventions + project shape

  • creates vertical-slice plan

  • returns exactly 3 target tests in structured format

agent action:"verify"

  • executes configured tests/lint/build per layer

  • checks branch naming + commit convention + TDD test budget

  • returns blocker list and final pass/fail report

agent action:"release"

  • checks CI status

  • parses commits since last tag

  • suggests semver impact (major / minor / patch)

  • can create tag and PR/MR (when enabled)

Local Data And Security

init generates:

  • .stackguide/config.json (project workflow config)

Runtime/local artifacts:

  • .stackguide/analysis-cache.json

  • .stackguide/health-history.json

These are machine-local and must not be committed.

Repository Guard

pnpm lint includes:

pnpm run guard:repo

The guard fails if .stackguide artifacts are tracked.

Integrity Hardening

Cache/history persistence includes:

  • boundary/symlink checks

  • file size and entry limits

  • atomic write strategy

  • checksum validation

  • optional HMAC signature using:

STACKGUIDE_INTEGRITY_KEY=<long-random-secret>

For teams, configure STACKGUIDE_INTEGRITY_KEY in local/dev and CI environments for stronger tamper resistance.

Supported Stacks

python-django, python-fastapi, python-flask, react-node, react-typescript, vue-node, nextjs, express, nestjs, laravel, rails, golang, rust, custom.

Development

Use pnpm for all commands.

pnpm install
pnpm lint
pnpm test
pnpm build
pnpm dev

Release And Version Policy

  • Current secure baseline: 4.1.2+

  • Versions from 3.0.0 up to 4.1.1 are deprecated in npm due to local artifact hygiene issues.

  • Use the latest 4.x release in all environments.

Registry Identifiers

  • npm package: @stackguide/mcp-server

  • MCP Registry server: io.github.isucorp-taimiralain/stackguide-mcp

License

GPL-3.0

Available Tools

16 tools
agentC

Active agent workflow actions: intake/plan/verify/release plus Jira ticket creation from strict MAIN DESCRIPTION templates.

Inputs: path, brief, action, labels, +22 more.

analyzeC

Project Intelligence: Comprehensive analysis of project structure, configuration, and dependencies. Provides smart recommendations, generates optimal configs, and suggests improvements based on framework best practices.

Inputs: path, action, format, autoFix, +1 more.

configC

Manage saved configurations: save, load, list, delete, export, or import.

Inputs: id, json, name, action.

contextA

Get current context with all loaded rules and knowledge. Use this to see what StackGuide has configured.

Inputs: full.

cursorB

Browse, search, and import rules from cursor.directory community.

Inputs: slug, query, action.

custom_ruleC

Create, update, delete, or list custom rules for your project.

Inputs: id, json, name, action, +2 more.

docsC

Fetch and manage web documentation. Fetch URLs, search cached docs, or list available.

Inputs: url, urls, query, action.

generateA

Generate boilerplate code from templates. Create components, hooks, services, tests, API routes, models, and utilities with best practices built in.

Inputs: name (required), type (required), options.

healthA

Get a comprehensive health score for your project. Analyzes configuration, code quality, structure, documentation, and testing readiness. Returns a grade (A-F) with detailed recommendations.

Inputs: detailed, projectPath.

helpC

Get help about StackGuide tools and how to use them.

Inputs: topic.

initB

Initialize a project with the StackGuide TDD workflow. Auto-detects your stack and scaffolds a .stackguide/ directory with only the relevant agents, skills and hooks.

Inputs: path, type, model, action, +6 more.

knowledgeB

Manage knowledge base: list, search, or get architecture patterns and solutions.

Inputs: query, action, category.

reviewA

Analyze code for issues using pattern matching. Detects security vulnerabilities, performance problems, coding standard violations, and architecture issues. Returns a score (0-100) and detailed report with suggestions. Works on files, URLs, or entire projects.

Inputs: url, file, focus, project.

rulesB

Manage rules: list, search, get, or select rules for your project.

Inputs: ids, query, action, category.

setupB

Configure StackGuide for your project. Auto-detects project type or lets you specify one manually.

Inputs: path, type, model, tokenMode, +5 more.

workflowC

TDD agentic workflow with lazy loading. Load agents, skills, hooks and commands on demand to save tokens. Five roles: Intake → Planner → Implementer → Verifier → Releaser.

Inputs: name, action, category.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 16 tools

    Disambiguation3/5

    Several tools have overlapping purposes: 'workflow' and 'agent' both handle TDD workflow actions; 'init' and 'setup' both configure the project; 'health', 'analyze', and 'review' all perform analysis. While descriptions provide some differentiation, an agent may still confuse similar tools.

    Naming Consistency2/5

    Tool names are a mix of verbs (generate, init, analyze, help, setup, review) and nouns (workflow, health, agent, context, rules, knowledge, cursor, docs, config, custom_rule). 'custom_rule' uses an underscore while all others are single words, showing no consistent naming pattern.

    Tool Count4/5

    With 16 tools, the server is slightly above the typical 3-15 range but still well-scoped for its broad feature set covering workflow, analysis, code generation, and configuration management. Each tool serves a clear purpose, and none seem redundant.

    Completeness4/5

    The tool set covers major aspects of a development assistant: project initialization, workflow management, code generation, health analysis, code review, rule management, documentation, and configuration. Minor gaps exist (e.g., no explicit deployment or testing automation), but overall it is comprehensive for its domain.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers