Derived-WMD

Derived-WMD exposes a Model Context Protocol (MCP) bridge that allows the Agent (Tambo-based) to inspect and modify your codebase autonomously. The MCP server provides filesystem visibility through tools like list_files and read_file, enabling the Agent to understand the current project layout before proposing changes. With this MCP integration, you can run the server locally and connect an MCP-enabled agent to enumerate files, read contents, and apply atomically validated file operations via the generateCode tool. Use the included BuildStatus, AppSpecSheet, and InteractableSandbox components in the Tambo UI to monitor progress, collect specifications, and preview changes in real time. The Agent can also manage the E2B sandbox to run and test changes in a secure environment, install dependencies, and fix build errors automatically based on build logs.

Prerequisites:

• Node.js 18+ installed on your machine
• pnpm (preferred) or npm
• Access to required API keys (E2B_API_KEY, NEXT_PUBLIC_TAMBO_API_KEY, FIRECRAWL_API_KEY optional, and LLM keys)

Installation steps:

1. Clone the repository:

git clone https://github.com/Sri-Krishna-V/Derived-WMD.git
cd Derived-WMD

2. Install dependencies (pnpm preferred):

pnpm install

3. Configure environment variables: Create a .env.local file with the following (fill in your keys):

# Required
E2B_API_KEY=your-e2b-api-key
NEXT_PUBLIC_TAMBO_API_KEY=your-tambo-key
GOOGLE_GENERATIVE_AI_API_KEY=your-google-key

# Optional
FIRECRAWL_API_KEY=your-firecrawl-key
ANTHROPIC_API_KEY=your-anthropic-key
OPENAI_API_KEY=your-openai-key

4. Run the development server:

pnpm dev

5. Access the app at: http://localhost:3000/ (or the port you configured)

Note: If you prefer Docker, you can adapt the project to run a containerized Next.js app and expose port 3000, then configure the MCP accordingly.

Tips and notes:

• Ensure all required API keys are available in your environment before starting.
• The MCP tools in Derived-WMD (list_files, read_file, generateCode, manageSandbox) enable the Agent to safely inspect and modify code with transaction rollbacks on failures.
• If you encounter build errors, check the E2B sandbox logs and ensure dependencies are installed before re-running generateCode operations.
• When running locally, the MCP_ENDPOINT should point to the local MCP bridge you start with the server.
• For security, keep your API keys out of version control and use environment-specific configs (e.g., .env.local).
• The Agent can render BuildStatus, AppSpecSheet, and InteractableSandbox components in the MCP-enabled chat to provide visibility into ongoing actions.
• If using Docker, ensure compatible Node.js version and expose port 3000 to your MCP client.