Daaem PMO MCP Server

MCP server for Daaem PMO V2 — enables AI agents to interact with PMO data.

Published on npm as @nozomtechs/daaem-pmo-mcp. See CHANGELOG.md for release history.

Install (end users)

// .mcp.json
{
  "mcpServers": {
    "daaem-pmo": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@nozomtechs/daaem-pmo-mcp@latest"],
      "env": {
        "DAAEM_TOKEN": "...",
        "DAAEM_URL": "https://pmo.nozomtechs.sa"
      }
    }
  }
}

Develop

npm install
npm run dev          # tsx watch mode
npm run build        # compile to dist/

Release workflow

Publishing to npm is automated via GitLab CI. To cut a release:

1. Make sure you're on main and up to date: git pull origin main
2. Bump the version — pick one:
   • Bug fix: npm version patch -m "chore: release v%s"
   • New feature: npm version minor -m "chore: release v%s"
   • Breaking change: npm version major -m "chore: release v%s"
3. Push commit + tag: git push && git push --tags

GitLab CI detects the vX.Y.Z tag, verifies it matches package.json, and publishes to npm automatically. Regular pushes and MRs only run npm ci (sanity check) — they do NOT publish.

One-time CI setup

Add the npm automation token as a GitLab CI variable:

• Settings → CI/CD → Variables → Add variable
• Key: NPM_TOKEN
• Value: automation token from npmjs.com → Tokens → Generate → Automation
• Flags: ✅ Masked, ✅ Protected
• Also protect the v* tag pattern in Settings → Repository → Protected Tags

Keeping the MCP in sync with PMO

Every new API endpoint or field on Daaem-PMO-V2 MUST be mirrored here in the same release cycle. See the gap log in Daaem-PMO-V2/CLAUDE.md for the rule.

Tool modules under src/tools/ map 1:1 to API resources — e.g. src/tools/expenses.ts ↔ /api/v1/workspaces/projects/{id}/expenses.