Skip to main content
Glama
DEPLOYMENT-READINESS.md3.83 kB
# Deployment Readiness Assessment ## ✅ Code Readiness ### Build Status - ✅ TypeScript compiles successfully - ✅ All dependencies defined in package.json - ✅ Build output exists in `dist/` directory - ✅ Start script configured: `npm start` → `node dist/index.js` ### Code Issues Checked - ✅ PORT handling: Uses `process.env.PORT || 3000` (Azure will set PORT automatically) - ✅ Environment variables: Code reads from `process.env` (Azure App Settings) - ✅ dotenv.config(): Present but harmless in Azure (won't find .env file, which is fine) - ✅ Error handling: Proper try/catch blocks - ✅ Async initialization: Server starts asynchronously (correct) ### Potential Issues - ⚠️ **Dependencies**: Azure needs to install `node_modules` before running - Solution: Deploy with `package.json` and let Azure install, OR pre-build locally - ⚠️ **Build Process**: Azure can build from source OR we deploy pre-built - Recommendation: Deploy pre-built for faster startup ## ✅ Azure Resources Status ### Existing - ✅ Resource Group: `Legal-MCP` (Canada Central) - ✅ App Service Plan: `Legal-MCP` (F1 Free tier, Canada Central) ### Need to Create - ❌ Storage Account: `legalmcpstore` - ❌ App Service (Web App): `legal-mcp` - ❌ Blob Containers: `documents`, `prompts` ## ⚠️ Configuration Requirements ### Environment Variables Needed 1. `AZURE_STORAGE_CONNECTION_STRING` - **MUST SET** (from storage account) 2. `ANTHROPIC_API_KEY` - **MUST SET** (from Anthropic console) 3. `PORT` - Azure sets automatically (defaults to 8080) 4. `NODE_ENV` - Should be "production" ### Azure App Service Configuration - Node.js version: Should be 20 LTS - Startup command: `npm start` (or can be auto-detected) - Always On: Not available on Free tier (app may sleep) ## 📋 Deployment Strategy ### Recommended: ZIP Deployment (Pre-built) **Pros:** - Faster deployment - No build time on Azure - More control over what's deployed **Steps:** 1. Build locally: `npm run build` 2. Install production deps: `npm ci --production` 3. Create ZIP with: `dist/`, `node_modules/`, `package.json` 4. Deploy ZIP to Azure ### Alternative: GitHub Deployment **Pros:** - Automatic deployments on push - Version control integration - Can trigger builds on Azure **Steps:** 1. Configure GitHub as source 2. Azure builds on deployment 3. Requires build configuration ## 🔍 Pre-Deployment Checklist ### Before Starting Deployment - [ ] Verify Azure CLI is logged in: `az account show` - [ ] Verify resource group exists: `az group show -n Legal-MCP` - [ ] Have Anthropic API key ready - [ ] Have storage account name available (legalmcpstore) - [ ] Code is committed to GitHub - [ ] Local build succeeds: `npm run build` ### During Deployment - [ ] Create storage account - [ ] Create blob containers (documents, prompts) - [ ] Upload prompt library - [ ] Create App Service - [ ] Configure environment variables - [ ] Deploy code - [ ] Verify deployment ### After Deployment - [ ] Check logs for errors - [ ] Test MCP endpoint - [ ] Verify tools are registered - [ ] Test document listing - [ ] Test prompt listing - [ ] Monitor for any runtime errors ## 🚨 Known Limitations (Free Tier) 1. **App Sleep**: Free tier apps sleep after 20 minutes of inactivity - First request after sleep may be slow - Consider Basic tier for production 2. **Compute Time**: 60 minutes per day limit - Monitor usage - Upgrade if needed 3. **No Custom Domain**: Free tier doesn't support custom domains - URL will be: `https://legal-mcp.azurewebsites.net` 4. **No Always On**: App may restart during inactivity - Sessions will be lost - Consider session persistence strategy if needed ## ✅ Ready to Deploy? **Status: READY** ✅ All code is ready. Proceed with deployment steps in DEPLOYMENT.md.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MCP-Agent766/Legal-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server