Context Engineering MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATA_DIR | No | Directory for persistent storage | ./data |
| NODE_ENV | No | Environment mode (development, production, test) | development |
| TEMPLATES_DIR | No | Directory containing internal templates | ./templates |
| EXTERNAL_TEMPLATES_DIR | No | Directory for Cole's external templates | ./external/context-engineering-intro |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_templatesA | List all available PRP templates with optional filtering by category |
| generate_prpA | Generate a Product Requirements Prompt based on a template and project context with storage integration |
| validate_prpC | Validate a PRP against context engineering best practices |
| search_templatesA | Search for templates by name, description, or tags |
| create_custom_templateC | Create a new custom PRP template |
| analyze_contextC | Analyze project context to recommend suitable templates and improvements |
| list_prpsC | List and search PRPs with advanced filtering and sorting capabilities |
| update_prpB | Update an existing PRP with change tracking and optional Archon synchronization |
| manage_storageC | Manage storage operations including versioning, change tracking, conflicts, and integrations |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Stakeholders (draft) | Initial request for Stakeholders - ** Customer Service |
| Csharp Patterns | Codebase patterns and conventions for csharp projects |
| Go Patterns | Codebase patterns and conventions for go projects |
| Java Patterns | Codebase patterns and conventions for java projects |
| Javascript Patterns | Codebase patterns and conventions for javascript projects |
| Kotlin Patterns | Codebase patterns and conventions for kotlin projects |
| Php Patterns | Codebase patterns and conventions for php projects |
| Python Patterns | Codebase patterns and conventions for python projects |
| Ruby Patterns | Codebase patterns and conventions for ruby projects |
| Rust Patterns | Codebase patterns and conventions for rust projects |
| Scala Patterns | Codebase patterns and conventions for scala projects |
| Swift Patterns | Codebase patterns and conventions for swift projects |
| Typescript Patterns | Codebase patterns and conventions for typescript projects |
| Sample Product Requirements Prompt | A sample PRP demonstrating the structure and content expected |
| Architecture Guidelines | Rules for system design and architecture |
| Coding Standards | Rules related to code quality and style |
| Deployment Standards | Rules for deployment and configuration |
| Documentation Standards | Rules for code and project documentation |
| Global Rules Collection | Complete set of project rules and guidelines |
| Testing Guidelines | Rules for testing practices and coverage |
| API Development Template | Template for REST API development with comprehensive validation and documentation |
| Template Collection | Complete collection of PRP templates |
| Base PRP Template v2 - Context-Rich with Validation Loops | Template optimized for AI agents to implement features with sufficient context and self-validation capabilities |
| Template Catalog | Searchable catalog of all templates with metadata |
| Template Categories | Templates organized by category |
| Popular Templates | Most frequently used templates |
| Web Application Feature Template | Template for web application features with React/TypeScript focus |
TDQS
Scored across 9 tools
Most tools have distinct purposes: analyze_context, generate_prp, validate_prp, etc. The only overlap is between list_templates and search_templates, which could cause confusion, but descriptions help differentiate browsing vs. searching.
All tool names follow a consistent verb_noun pattern (analyze_context, list_templates, generate_prp, etc.). No mixed conventions or vague verbs.
9 tools is well within the ideal 3-15 range and each tool contributes to the template and PRP lifecycle. The count feels appropriate for the server's scope.
The tool surface covers template listing/searching/creation and PRP generation/validation/listing/update, but lacks delete operations for both templates and PRPs. Also, there is no direct 'get_prp' by ID, though list_prps may suffice. These are notable gaps for a management server.