context-engineering

The Context Engineering MCP Server automates the creation of high-quality Product Requirements Prompts (PRPs) by analyzing your codebase and applying Cole Medin’s context engineering methodology. It exposes a suite of tools designed to generate PRPs, validate them against best practices, and manage stored PRPs, all while integrating with Archon for task and knowledge management. Use the available commands to list templates, generate PRPs tailored to your project context, search and create templates, analyze your project, and manage storage and versions. The server helps you start with informed, context-aware requirements rather than blank documents, producing actionable PRPs that reflect your current tech stack and constraints.

Prerequisites:

• Node.js (LTS) and npm installed on your system
• Git for cloning the repository

Install steps:

1. Clone the repository git clone https://github.com/locomotive-agency/context-engineering-mcp.git cd context-engineering-mcp

2. Install dependencies npm install

3. Build the TypeScript code npm run build

4. Start the MCP server npm start

Optional for development:

• Run in watch mode (if configured): npm run watch
• Use a demo integration script if provided (e.g., node demo-integration.js)

Notes:

• Ensure your environment variables (TEMPLATES_DIR, EXTERNAL_TEMPLATES_DIR, DATA_DIR) are correctly set if you deviate from defaults.

Tips and common issues:

• Ensure the templates directories exist; otherwise the server may fail to load templates on startup.
• If you override DATA_DIR, ensure the path is writable by the running process to avoid storage errors.
• The MCP protocol version is v0.6.0; verify client compatibility if connecting from external tools.
• For Claude Desktop integration, configure the MCP server path to the built dist/index.js and set env vars accordingly.
• When updating templates or PRP templates, consider running the template synchronization script (e.g., scripts/sync-templates.sh) to keep upstream templates current.
• If you encounter type errors during build, ensure your TypeScript version matches the project’s configuration and run npm ci to clean install exact versions.