StackGuide MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STACKGUIDE_INTEGRITY_KEY | No | Optional secret key for HMAC signature of cache/history files for integrity hardening. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| setupB | Configure StackGuide for your project. Auto-detects project type or lets you specify one manually. |
| contextA | Get current context with all loaded rules and knowledge. Use this to see what StackGuide has configured. |
| rulesB | Manage rules: list, search, get, or select rules for your project. |
| knowledgeB | Manage knowledge base: list, search, or get architecture patterns and solutions. |
| 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. |
| cursorB | Browse, search, and import rules from cursor.directory community. |
| docsC | Fetch and manage web documentation. Fetch URLs, search cached docs, or list available. |
| configC | Manage saved configurations: save, load, list, delete, export, or import. |
| custom_ruleC | Create, update, delete, or list custom rules for your project. |
| helpC | Get help about StackGuide tools and how to use them. |
| generateA | Generate boilerplate code from templates. Create components, hooks, services, tests, API routes, models, and utilities with best practices built in. |
| 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. |
| workflowB | TDD agentic workflow with lazy loading. Load agents, skills, hooks, commands, scripts and the OJ policy on demand to save tokens. Five roles: Intake → Planner → Implementer → Verifier → Releaser. |
| initA | Initialize a project with the StackGuide TDD workflow. Auto-detects your stack and scaffolds a .stackguide/ directory with only the relevant agents, skills, hooks and scripts (including the optional OJ health gate). |
| agentC | Active agent workflow actions: intake/plan/verify/release plus Jira ticket creation from strict MAIN DESCRIPTION templates. |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| welcome | Get started with StackGuide - interactive setup wizard |
| configure_project | Smart project configuration with auto-detection and suggestions |
| code_review | Review code from file, URL, or pasted code against active rules |
| apply_patterns | Apply architecture patterns from knowledge base |
| tdd_intake | Activate the Task Intake agent — reads a ticket and produces a brief for the Planner |
| tdd_plan | Activate the TDD Planner agent — produces a test-first plan with 3 tests for a vertical slice |
| tdd_implement | Activate the TDD Implementer agent — executes Red → Green → Refactor for the planned tests |
| tdd_verify | Activate the Verifier agent — runs the quality gate checklist before the MR |
| tdd_release | Activate the Releaser agent — safely tags, generates release notes and publishes |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Express.js - All Rules | All coding rules for express projects |
| Go - All Rules | All coding rules for golang projects |
| Laravel PHP - All Rules | All coding rules for laravel projects |
| NestJS - All Rules | All coding rules for nestjs projects |
| Next.js - All Rules | All coding rules for nextjs projects |
| Python Django - All Rules | All coding rules for python-django projects |
| Python FastAPI - All Rules | All coding rules for python-fastapi projects |
| Python Flask - All Rules | All coding rules for python-flask projects |
| Ruby on Rails - All Rules | All coding rules for rails projects |
| React with Node.js - All Rules | All coding rules for react-node projects |
| React TypeScript - All Rules | All coding rules for react-typescript projects |
| Rust - All Rules | All coding rules for rust projects |
| Vue.js with Node.js - All Rules | All coding rules for vue-node projects |
| Express.js - Knowledge Base | Knowledge base for express projects |
| Go - Knowledge Base | Knowledge base for golang projects |
| Laravel PHP - Knowledge Base | Knowledge base for laravel projects |
| NestJS - Knowledge Base | Knowledge base for nestjs projects |
| Next.js - Knowledge Base | Knowledge base for nextjs projects |
| Python Django - Knowledge Base | Knowledge base for python-django projects |
| Python FastAPI - Knowledge Base | Knowledge base for python-fastapi projects |
| Python Flask - Knowledge Base | Knowledge base for python-flask projects |
| Ruby on Rails - Knowledge Base | Knowledge base for rails projects |
| React with Node.js - Knowledge Base | Knowledge base for react-node projects |
| React TypeScript - Knowledge Base | Knowledge base for react-typescript projects |
| Rust - Knowledge Base | Knowledge base for rust projects |
| Vue.js with Node.js - Knowledge Base | Knowledge base for vue-node projects |
| Active Context | The currently active project context with selected rules and knowledge |
| Rule Templates | Available templates for creating new rules |
TDQS
Scored across 16 tools
Several tools have overlapping purposes: knowledge, rules, custom_rule, and cursor all involve managing rules or knowledge, while review, analyze, and health all analyze project quality. Workflow, init, and agent also cover overlapping workflow functionality, making it difficult to choose the correct tool.
All tool names are lowercase with underscores for multi-word names, but there is no consistent verb-noun pattern. Names mix verbs (generate, review, analyze) and nouns (health, context, workflow), and some are ambiguous (setup vs init, agent vs workflow).
With 16 tools, the count is slightly above the typical 3-15 range but reasonable given the broad scope of the server (project setup, code analysis, workflow management). Each tool appears to serve a distinct purpose in the overall system.
The tool surface covers major workflows like code review, project analysis, rule management, and TDD workflow initialization. However, knowledge management lacks create/update/delete operations, and there is no obvious way to manage docs entries beyond fetching/searching, leaving some gaps.