# β
EX MCP Server - Auggie CLI Setup Guide
## π§ Secure Configuration
The MCP server is now properly configured for Auggie CLI with secure environment variable handling.
## β
Final Configuration
The configuration uses environment variables for API keys and a wrapper for reliable startup:
```json
{
"mcpServers": {
"ex": {
"command": "python",
"args": ["mcp_server_wrapper.py"],
"cwd": "/Users/ajjoobandi/Development/ex-mcp-server",
"env": {
"PYTHONPATH": "/Users/ajjoobandi/Development/ex-mcp-server"
}
}
}
}
```
## π Security Setup
**IMPORTANT**: API keys are now stored securely in environment variables, not in the configuration file.
1. **Copy the environment template:**
```bash
cp .env.example .env
```
2. **Edit .env with your actual API keys:**
```bash
# Add at least one API key
KIMI_API_KEY=your-actual-kimi-key
GLM_API_KEY=your-actual-glm-key
OPENROUTER_API_KEY=your-actual-openrouter-key
```
## π Ready to Use
The server is now fully compatible with auggie CLI:
```bash
# Use with auggie CLI (make sure .env file exists with your API keys)
auggie --mcp-config /Users/ajjoobandi/Development/ex-mcp-server/auggie-config.json
```
## π Configuration Files
- **`auggie-config.json`** - Your personalized configuration with absolute paths
- **`auggie-config.example.json`** - Template for creating your own configuration
- **`.env`** - Your API keys and environment variables (create from `.env.example`)
## π Available Tools
All 16 AI-powered development tools are available:
- **chat** - Interactive development chat
- **thinkdeep** - Step-by-step deep thinking
- **planner** - Interactive sequential planning
- **consensus** - Multi-model consensus analysis
- **codereview** - Comprehensive code review
- **precommit** - Pre-commit validation
- **debug** - Root cause analysis
- **secaudit** - Security audit
- **docgen** - Documentation generation
- **analyze** - General file analysis
- **refactor** - Code refactoring
- **tracer** - Call flow analysis
- **testgen** - Test generation
- **challenge** - Critical thinking prompts
- **listmodels** - Model listing
- **version** - Server information
## π Verification
```bash
# Test server startup
python mcp_server_wrapper.py
# Verify configuration
python debug_mcp.py
# Use with auggie (ensure .env file exists)
auggie --mcp-config auggie-config.json
```
## β
Success Indicators
- β
Server starts with minimal output
- β
16 tools loaded successfully
- β
API keys securely stored in .env file
- β
MCP protocol communication working
- β
Ready for auggie CLI integration
## π Security Notes
- β
API keys removed from configuration files
- β
Environment variables used for sensitive data
- β
.env.example provided as template
- β
Repository is now safe to push to remote
The MCP server is properly configured with security best practices and ready for seamless integration with the auggie CLI!