Power Platform Mcp Connector Suite
Scaffold a Copilot Studio–ready Power Platform custom connector that speaks MCP (streamable JSON-RPC), with schemas, C# script transforms, and compliance checks for agentic tools.
Overview
Power Platform MCP Connector Suite is an agent skill for the Build phase that generates a complete Power Platform custom connector with MCP integration for Microsoft Copilot Studio, including schema generation and valida
Install
npx skills add https://github.com/github/awesome-copilot --skill power-platform-mcp-connector-suiteWhat is this skill?
- Generates `apiDefinition.swagger.json` with `x-ms-agentic-protocol: mcp-streamable-1.0` and POST `/mcp` JSON-RPC endpoin
- Ships `apiProperties.json`, `script.csx` for MCP JSON-RPC handling, and connector `readme.md`
- Documents Copilot Studio limits: Tools and Resources (as tool outputs) supported; Prompts not yet supported
- Validates schemas for no `$ref` in tool inputs/outputs and single-type constraints
- Includes troubleshooting guidance for schema compliance with Copilot Studio
- Copilot Studio MCP support documented for Tools and Resources; Prompts listed as not yet supported
Adoption & trust: 8.4k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have MCP tools you want in Copilot Studio but Power Platform connectors reject non-compliant OpenAPI and JSON-RPC shapes.
Who is it for?
Builders targeting Copilot Studio who need MCP-backed custom connectors with agentic protocol headers and Studio-safe single-type schemas.
Skip if: Non-Microsoft agent stacks (plain Claude Code MCP only with no Power Platform), or teams that only need a REST API without MCP JSON-RPC on `/mcp`.
When should I use this skill?
You need to generate a complete Power Platform custom connector with MCP integration, schema generation, troubleshooting, and validation for Copilot Studio.
What do I get? / Deliverables
You get a documented connector file set—Swagger, properties, script.csx—that aligns with MCP streamable protocol and Copilot Studio schema rules ready to import and test.
- apiDefinition.swagger.json with MCP streamable protocol annotation
- apiProperties.json and script.csx for JSON-RPC handling
- Connector readme.md with integration notes
Recommended Skills
Journey fit
Build is primary because the skill produces connector artifacts—Swagger, apiProperties, script.csx, and docs—not production monitoring or go-to-market work. Agent-tooling matches Microsoft Copilot Studio MCP integration: wiring external tool protocols into the agent runtime rather than generic CRUD APIs alone.
How it compares
Skill-packaged connector codegen for Power Platform—not a hosted MCP server and not a generic OpenAPI generator that ignores Copilot Studio agentic constraints.
Common Questions / FAQ
Who is power-platform-mcp-connector-suite for?
Solo builders and indie teams shipping Copilot Studio agents who must expose MCP servers as first-class custom connectors with valid schemas.
When should I use power-platform-mcp-connector-suite?
During Build agent-tooling when you are defining POST `/mcp` JSON-RPC, generating apiDefinition and script.csx, or fixing connector import errors before pilot users touch the agent.
Is power-platform-mcp-connector-suite safe to install?
It generates connector definitions that may embed endpoint URLs and auth patterns—review outputs before publishing; check the Security Audits panel on this Prism page for the package source.
SKILL.md
READMESKILL.md - Power Platform Mcp Connector Suite
# Power Platform MCP Connector Suite Generate comprehensive Power Platform custom connector implementations with Model Context Protocol integration for Microsoft Copilot Studio. ## MCP Capabilities in Copilot Studio **Currently Supported:** - ✅ **Tools**: Functions that the LLM can call (with user approval) - ✅ **Resources**: File-like data that agents can read (must be tool outputs) **Not Yet Supported:** - ❌ **Prompts**: Pre-written templates (prepare for future support) ## Connector Generation Create complete Power Platform connector with: **Core Files:** - `apiDefinition.swagger.json` with `x-ms-agentic-protocol: mcp-streamable-1.0` - `apiProperties.json` with connector metadata and authentication - `script.csx` with custom C# transformations for MCP JSON-RPC handling - `readme.md` with connector documentation **MCP Integration:** - POST `/mcp` endpoint for JSON-RPC 2.0 communication - McpResponse and McpErrorResponse schema definitions - Copilot Studio constraint compliance (no reference types, single types) - Resource integration as tool outputs (Resources and Tools supported; Prompts not yet supported) ## Schema Validation & Troubleshooting **Validate schemas for Copilot Studio compliance:** - ✅ No reference types (`$ref`) in tool inputs/outputs - ✅ Single type values only (not `["string", "number"]`) - ✅ Primitive types: string, number, integer, boolean, array, object - ✅ Resources as tool outputs, not separate entities - ✅ Full URIs for all endpoints **Common issues and fixes:** - Tools filtered → Remove reference types, use primitives - Type errors → Single types with validation logic - Resources unavailable → Include in tool outputs - Connection failures → Verify `x-ms-agentic-protocol` header ## Context Variables - **Connector Name**: [Display name for the connector] - **Server Purpose**: [What the MCP server should accomplish] - **Tools Needed**: [List of MCP tools to implement] - **Resources**: [Types of resources to provide] - **Authentication**: [none, api-key, oauth2, basic] - **Host Environment**: [Azure Function, Express.js, etc.] - **Target APIs**: [External APIs to integrate with] ## Generation Modes ### Mode 1: Complete New Connector Generate all files for a new Power Platform MCP connector from scratch, including CLI validation setup. ### Mode 2: Schema Validation Analyze and fix existing schemas for Copilot Studio compliance using paconn and validation tools. ### Mode 3: Integration Troubleshooting Diagnose and resolve MCP integration issues with Copilot Studio using CLI debugging tools. ### Mode 4: Hybrid Connector Add MCP capabilities to existing Power Platform connector with proper validation workflows. ### Mode 5: Certification Preparation Prepare connector for Microsoft certification submission with complete metadata and validation compliance. ### Mode 6: OAuth Security Hardening Implement OAuth 2.0 authentication enhanced with MCP security best practices and advanced token validation. ## Expected Output **1. apiDefinition.swagger.json** - Swagger 2.0 format with Microsoft extensions - MCP endpoint: `POST /mcp` with proper protocol header - Compliant schema definitions (primitive types only) - McpResponse/McpErrorResponse definitions **2. apiProperties.json** - Connector metadata and branding (`iconBrandColor` required) - Authentication configuration - Policy templates for MCP transformations **3. script.csx** - JSON-RPC 2.0 message handling - Request/response transformations - MCP protocol compliance logic - Error handling and validation **4. Implementation guidance** - Tool registration and execution patterns - Resource management strategies - Copilot Studio integration steps - Testing and validation procedures ## Validation Checklist ### Technical Complian