MongoDB Setup
The ADM Toolkit uses MongoDB for persistence. All writes happen through the MCP server tools; the docs site and portfolio dashboard (in the main app) are read-only.
Create a Cluster​
- Go to MongoDB Atlas
- Create a free cluster (M0)
- Create a database user with read/write access
- Add your IP to the network access list (or use
0.0.0.0/0for development) - Get the connection string:
mongodb+srv://user:pass@cluster.mongodb.net/
Configure​
Add to .env (and optionally .env.local) in the project root:
MONGODB_URI=mongodb+srv://user:password@cluster.mongodb.net/?retryWrites=true&w=majority
MONGODB_DB=adm_toolkit
- MCP server and seed script read from
.env(and.env.localif present) - Next.js app (Portfolio page) reads from
.env.localor.env
For the Portfolio page at /portfolio to show data, ensure MONGODB_URI is in .env.local so the Next.js app can connect.
Vercel deployment: Add MONGODB_URI in Project Settings → Environment Variables. Avoid common mistakes:
- No quotes around the value
- URL-encode special characters in the password (e.g.
!→%21,@→%40) - No trailing spaces or newlines — paste carefully
The MCP server creates collections and indexes on first connect.
Collections​
| Collection | Purpose |
|---|---|
accounts | Account intelligence (from adm_account_research) |
health_scores | Health score history |
adoption_reports | Adoption metrics over time |
metrics_models | DORA metrics models |
roi_models | ROI calculations |
deployment_plans | Phased deployment plans |
playbooks | Deployment playbooks |
escalations | Escalation briefs |
competitive | Competitive landscape data |
See MongoDB Collections for full schema details.