DHIS2 MCP Server

Instructions

Implementation Reference

• src/index.ts:1578-1595 (handler)

  Handler implementation for the 'dhis2_get_composition_examples' tool. Delegates to MultiServerComposition.generateIntegrationExamples() and formats the response.
  case 'dhis2_get_composition_examples': const examples = multiServerComposition.generateIntegrationExamples(); auditLogger.log({ toolName: name, parameters: {}, outcome: 'success', dhis2Instance: dhis2Client?.baseURL, userId: currentUser?.username, executionTime: Date.now() - startTime }); return { content: [{ type: 'text', text: examples }] };
• src/multi-server-composition.ts:142-264 (helper)

  Core implementation: generateIntegrationExamples() method returns comprehensive Markdown documentation with workflow examples, Mermaid diagrams, JSON workflow templates, and integration instructions for multi-server compositions.
  generateIntegrationExamples(): string { return `# DHIS2 MCP Server - Multi-Server Integration Examples ## 🔗 Compatible Server Integrations ${this.compatibleServers.size > 0 ? Array.from(this.compatibleServers.values()).map(server => `### ${server.name} **Capabilities**: ${server.capabilities.map(cap => cap.domain).join(', ')} **Version**: ${server.version} `).join('\n') : 'No compatible servers registered yet.'} ## 🚀 Workflow Examples ### 1. Data Quality Monitoring \`\`\`mermaid graph LR A[DHIS2: Run Validation] --> B[GitHub: Create Issue] B --> C[Slack: Notify Team] C --> D[Database: Log Issue] \`\`\` ### 2. Development Pipeline \`\`\`mermaid graph LR A[DHIS2: Generate App] --> B[Git: Commit Changes] B --> C[GitHub: Create PR] C --> D[Slack: Request Review] \`\`\` ### 3. Data Export Pipeline \`\`\`mermaid graph LR A[DHIS2: Export Data] --> B[Database: Store Copy] B --> C[Email: Send Report] C --> D[Filesystem: Archive] \`\`\` ## 🛠️ Cross-Server Tool Examples ### Data Quality → Issue Tracking \`\`\`json { "workflow": "data-quality-monitoring", "steps": [ { "server": "dhis2-mcp", "tool": "dhis2_run_validation", "parameters": { "orgUnit": "country-level" } }, { "server": "github-mcp", "tool": "create_issue", "parameters": { "title": "Data Quality Issues Found", "body": "{{previous.validationResults}}" } } ] } \`\`\` ### Development → Deployment \`\`\`json { "workflow": "app-deployment", "steps": [ { "server": "dhis2-mcp", "tool": "dhis2_init_webapp", "parameters": { "appName": "patient-tracker" } }, { "server": "git-mcp", "tool": "commit_changes", "parameters": { "message": "Initial app scaffolding" } }, { "server": "slack-mcp", "tool": "send_message", "parameters": { "message": "New DHIS2 app created: {{step1.appName}}" } } ] } \`\`\` ## 📊 Integration Benefits 1. **Automated Workflows**: Chain DHIS2 operations with external systems 2. **Enhanced Monitoring**: Connect DHIS2 analytics to notification systems 3. **Development Integration**: Seamless connection to development toolchains 4. **Data Pipeline**: Build comprehensive data processing workflows 5. **Quality Assurance**: Automated testing and validation across systems ## 🔧 Setup Instructions 1. **Start DHIS2 MCP Server**: This server (already running) 2. **Start Compatible Servers**: GitHub, Slack, Database, etc. 3. **Configure Client**: Point MCP client to all servers 4. **Define Workflows**: Create cross-server automation rules 5. **Test Integration**: Verify data flows between servers ## 📝 Data Exchange Format All data exported from DHIS2 MCP follows this standard format: \`\`\`json { "sourceServer": "dhis2-mcp", "timestamp": "2024-01-01T00:00:00.000Z", "operationType": "export", "metadata": { "toolName": "dhis2_get_analytics", "dhis2Instance": "https://play.dhis2.org", "dataType": "analytics" }, "data": { "/* DHIS2 response data */" } } \`\`\` This standardized format ensures seamless integration with other MCP servers.`;