Power Agent MCP

🎯 Overview

Power Agent MCP is a production-ready Model Context Protocol (MCP) server providing AI assistants with programmatic access to core Microsoft Power Platform operations. The current implementation focuses on essential Power Platform CLI operations including environment management and solution lifecycle automation, delivering a solid foundation for AI-driven Power Platform automation.

Current Implementation:

• Standalone Mode: 12 core Power Platform tools covering essential operations
• Enterprise Mode: Extensible architecture ready for additional tool categories

🆕 What's New - Standalone Production Release

Latest Release: Production-ready standalone MCP server with core Power Platform automation capabilities.

🔥 Current Implementation - Core 12 Tools

• ✅ Authentication Management: Service Principal and user authentication (3 tools)
• ✅ Environment Operations: Create, list, delete environments (3 tools)
• ✅ Solution Lifecycle: Export, import, pack, unpack solutions (4 tools)
• ✅ Status & Diagnostics: Connection validation and health checks (2 tools)

Current Capabilities

• 12 Production-Ready Tools providing essential Power Platform automation
• Environment Lifecycle - Create, list, and manage Power Platform environments
• Solution Management - Export, import, pack, and unpack solutions with full DevOps support
• Authentication Management - Create and manage multiple authentication profiles
• PAC CLI Integration - Direct integration with Microsoft Power Platform CLI

See Complete Tool Reference for detailed documentation.

🏗️ SDK Architecture & Coverage

Enterprise SDK Benefits

• 🤖 Natural Language API: Describe operations in plain English - no CLI memorization required
• 📈 Core Platform Coverage: Essential Power Platform capabilities accessible through AI
• 🏢 Production-Grade Security: Service Principal authentication and secure credential management
• 🔧 Zero Learning Curve: AI handles syntax, parameters, and orchestration automatically
• 🚀 Extensible Framework: Proven patterns for integrating additional enterprise systems
• 🎨 AI-First Design: Optimized for conversational workflows and automation chains

📋 SDK Component Overview

✅ SDK Validation & Testing Coverage

🧪 Continuous Integration Results

✅ Tool Schema Validation: 12/12 valid implementations
✅ Handler Integration: 12/12 active handlers  
✅ Power Platform Coverage: 12/12 PAC CLI mappings verified
✅ Documentation: 100% API reference complete with examples
✅ Enterprise Authentication: Service Principal verified
✅ Server Startup: Standalone server operational
✅ CLI Integration: PAC CLI commands executing successfully

🚀 Quick Start

Prerequisites

• Node.js 18+ and npm
• Power Platform CLI (installation guide)
• Valid Microsoft 365 or Power Platform license
• Claude Desktop or compatible MCP client

Installation

1. Clone and Setup

   git clone https://github.com/dayour/Power-Agent-MCP.git
   cd Power-Agent-MCP
   npm install
   npm run build
   

2. Configure Authentication

   Create a service principal for production use:

   # Register application in Azure AD
   az ad app create --display-name "Power-Agent-MCP"
   
   # Note the Application ID from the response and create client secret
   az ad app credential reset --id your-application-id
   

   Example response:

   {
     "appId": "your-application-id",
     "password": "your-client-secret",
     "tenant": "your-tenant-id"
   }
   

Current Tool Set (12 Tools)

Authentication & Connection (3 tools):

• pp_whoami - Check authentication status and current environment
• pp_auth_create - Create new authentication profiles
• pp_auth_list - List available authentication profiles
• pp_auth_select - Switch between authentication profiles

Environment Management (3 tools):

• pp_create_environment - Create new Power Platform environments
• pp_list_environments - List all available environments
• pp_delete_environment - Delete environments (with confirmation)

Solution Operations (4 tools):

• pp_export_solution - Export solutions (managed or unmanaged)
• pp_import_solution - Import solutions to environments
• pp_pack_solution - Package solutions for deployment
• pp_unpack_solution - Unpack solutions for source control

Example Commands:

"Check my current Power Platform connection status"
"Create a development environment called 'Team Workspace' in the US region"
"Export the 'CustomerPortal' solution as a managed solution"
"List all my Power Platform environments"

3. Setup Claude Desktop

   Add to your claude_desktop_config.json:

   {
     "mcpServers": {
       "power-agent-mcp": {
         "command": "node",
         "args": ["/path/to/Power-Agent-MCP/dist/mcp/server.js"],
         "env": {
           "POWERPLATFORM_TENANT_ID": "your-tenant-id",
           "POWERPLATFORM_APPLICATION_ID": "your-app-id",
           "POWERPLATFORM_CLIENT_SECRET": "your-client-secret"
         }
       }
     }
   }
   

4. Start Using with AI

   Open Claude Desktop and try:

   "Check my Power Platform authentication status"
   "Create a new development environment called 'AI Innovation Lab' in East US region"
   "List all my Power Platform environments and their status"
   "Export the CustomerPortal solution and pack it for deployment"
   

💡 Quick Tip: The current implementation provides 12 core tools for essential Power Platform automation. Additional tools and capabilities are available in the roadmap for future releases.

📚 Complete SDK Reference

📋 Component-Specific Guides

📖 Complete Implementation Reports

• Comprehensive PAC CLI Audit - Complete CLI mapping verification
• Copilot Coverage Audit - AI integration validation
• MCP Functionality Report - End-to-end functionality analysis

💬 Integration & Setup

Prerequisites

• Node.js 18+ and npm package manager
• Power Platform CLI (installation guide)
• Valid Microsoft 365 or Power Platform license with appropriate permissions
• Claude Desktop or compatible MCP client (supported clients)

Installation & Configuration

# Clone the repository
git clone https://github.com/dayour/Power-Agent-MCP.git
cd Power-Agent-MCP

# Install dependencies and build
npm install
npm run build

# Verify installation
npm test

# Register application in Azure AD
az ad app create --display-name "Power-Agent-MCP-Production"

# Get Application ID and create client secret
az ad app credential reset --id <APPLICATION_ID>

# Grant Power Platform permissions
az ad app permission add --id <APPLICATION_ID> --api 00000007-0000-0000-c000-000000000000

export POWERPLATFORM_TENANT_ID="your-tenant-id"
export POWERPLATFORM_APPLICATION_ID="your-app-id"
export POWERPLATFORM_CLIENT_SECRET="your-client-secret"

{
  "mcpServers": {
    "power-agent-mcp": {
      "command": "node",
      "args": ["/path/to/Power-Agent-MCP/dist/mcp/server.js"],
      "env": {
        "POWERPLATFORM_TENANT_ID": "your-tenant-id",
        "POWERPLATFORM_APPLICATION_ID": "your-app-id",
        "POWERPLATFORM_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

"List all my Power Platform environments"
"Show me the available Dataverse tools"
"Create a test adaptive card for customer feedback"

💡 Usage Examples

Human: "Create a new development environment for my team called 'Customer Portal Dev' in the United States region"

AI: I'll create a development environment for you:

*Uses pp_create_environment with appropriate parameters*

Environment "Customer Portal Dev" created successfully:
- ✅ Development type for safe experimentation
- 🌎 Located in United States region
- 🔗 Environment URL: https://customerportaldev.crm.dynamics.com/
- 🆔 Environment ID: 12345678-1234-1234-1234-123456789012

Your development environment is ready for use!

Human: "Export our CustomerPortal solution as managed and pack it for deployment"

AI: I'll export and package your solution for deployment:

Step 1: Exporting solution
*Uses pp_export_solution with managed=true*

Step 2: Packaging for deployment
*Uses pp_pack_solution for distribution*

Solution deployment package created:
- 📦 CustomerPortal_1_0_0_0_managed.zip exported
- 🔄 Packaged for production deployment
- ✅ Ready for import to target environment

Your solution is ready for deployment!

Human: "Set up authentication for our production environment and check connection status"

AI: I'll configure authentication and verify the connection:

Step 1: Authentication Setup
*Uses pp_auth_create with Service Principal credentials*

Step 2: Connection Verification
*Uses pp_whoami to validate connection*

Authentication configured successfully:
- 🔐 Service Principal authentication active
- 🌐 Connected to: https://prod.crm.dynamics.com/
- ✅ Connection validated and ready
- 👤 Authenticated as: powerapp-service@company.com

Your production environment connection is ready!

🔧 Enterprise SDK Architecture

graph TB
    AI[AI Assistant<br/>Claude Desktop] --> MCP[MCP Protocol Layer]
    MCP --> PAM[Power Agent MCP SDK<br/>12 Core Tools]

    PAM --> PP[Power Platform CLI<br/>12 Core Commands]
    PAM --> FUTURE[Future Extensions<br/>Roadmap]

    PP --> AUTH[Authentication<br/>3 Tools]
    PP --> ENV[Environment Ops<br/>3 Tools]
    PP --> SOL[Solution Dev<br/>4 Tools]
    PP --> DIAG[Diagnostics<br/>2 Tools]

    FUTURE --> DV[Dataverse Operations<br/>Planned]
    FUTURE --> SQL[SQL Server SDK<br/>Planned]
    FUTURE --> AC[Adaptive Cards<br/>Planned]
    FUTURE --> EXTEND[Additional SDKs<br/>Extensible]

    PAM --> EXT[Extensible Framework<br/>Ready for Extensions]

    style AI fill:#e1f5fe
    style PAM fill:#f3e5f5
    style PP fill:#e8f5e8
    style FUTURE fill:#fff3e0
    style AUTH fill:#fce4ec
    style ENV fill:#e0f2f1
    style SOL fill:#f3e5f5
    style DIAG fill:#e1f5fe

🏗️ SDK Architecture Principles

🛠️ SDK Extension Framework

Adding New Enterprise Integrations:

1. Tool Interface Creation - Follow established TypeScript patterns in src/mcp/tools/
2. Authentication Layer - Implement secure credential management
3. Error Handling - Add comprehensive validation and recovery
4. Documentation - Create API reference with examples
5. Testing - Implement unit and integration tests

Example Integration Pattern:

// src/mcp/tools/sharepoint.ts
export const sharepointTools: Tool[] = [
  {
    name: "pp_sharepoint_site_create",
    description: "Create new SharePoint site",
    inputSchema: {
      type: "object",
      properties: {
        siteName: { type: "string" },
        template: { type: "string" }
      }
    }
  }
];

See Architecture Guide for detailed extension patterns.

🤝 Contributing to the SDK

📋 Enterprise Development Guidelines

• Security First - All tools must implement proper authentication and validation
• Documentation Complete - Every tool requires API reference and usage examples
• Production Ready - Comprehensive error handling and recovery mechanisms
• Extensible Design - Follow established patterns for future integration ease
• Test Coverage - Unit tests and integration tests for all new functionality

For detailed contribution guidelines and SDK patterns, see CONTRIBUTING.md.

📊 SDK Impact & Metrics

🎯 Production Adoption Metrics

• 📈 12 Core Tools Available - Essential Power Platform automation coverage
• 🏢 Enterprise Authentication - Service Principal authentication support
• 🤖 AI Integration Ready - Optimized for Claude Desktop and MCP clients
• 📚 Complete Documentation - 100% API reference with examples
• 🔒 Security Validated - Enterprise-grade compliance and audit trails
• ⚡ Production Ready - Standalone server operational and tested

📄 Legal & Compliance

🔒 Security

Security issues should be reported following our Security Policy. Please do not report security vulnerabilities through public GitHub issues.

📜 Code of Conduct

This project follows the Microsoft Open Source Code of Conduct. By participating, you agree to uphold this code.

⚖️ License

This project is licensed under the MIT License - see the LICENSE file for details.

🏷️ Trademarks

This project may contain trademarks or logos for projects, products, or services. Use of Microsoft trademarks or logos must follow Microsoft's Trademark & Brand Guidelines.