Skip to content
Skillpedia
Agents40k · #5282

power-platform-mcp-connector-suite

Lets your agent create custom connectors for Power Platform. It helps integrate Copilot Studio, generating the schema and ensuring everything works well.

What it does

This tool creates a connector for Power Platform that allows Copilot Studio to interact with other tools and data. It ensures everything is set up correctly so Copilot Studio can effectively use these tools and data.

When to use it

  • ✓When you want Copilot Studio to use external tools.
  • ✓When you need Copilot Studio to read files or data.
  • ✓When you want to ensure your connector works well with Copilot Studio.

Example of what to ask your AI

“Create a connector so Copilot Studio can fetch customer information and analyze trends, using the tools 'searchCustomers' and 'analyzeTrends'.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/github/awesome-copilot/blob/main/skills/power-platform-mcp-connector-suite/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/github/awesome-copilot/blob/main/skills/power-platform-mcp-connector-suite/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool generates the necessary files for the connector, such as API definitions and scripts. It also checks if the connector follows Copilot Studio's rules so it can understand and use the tools and data you provide.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add github/awesome-copilot --skill power-platform-mcp-connector-suite

Or download just the file:

curl -L https://raw.githubusercontent.com/github/awesome-copilot/main/skills/power-platform-mcp-connector-suite/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

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 Compliance

  • x-ms-agentic-protocol: mcp-streamable-1.0 in MCP endpoint
  • No reference types in any schema definitions
  • All type fields are single types (not arrays)
  • Resources included as tool outputs
  • JSON-RPC 2.0 compliance in script.csx
  • Full URI endpoints throughout
  • Clear descriptions for Copilot Studio agents
  • Authentication properly configured
  • Policy templates for MCP transformations
  • Generative Orchestration compatibility

CLI Validation

  • paconn validate: paconn validate --api-def apiDefinition.swagger.json passes without errors
  • pac CLI ready: Connector can be created/updated with pac connector create/update

…

FAQ

What are 'Tools' and 'Resources'?

'Tools' are like functions that Copilot Studio can call to perform actions. 'Resources' are data that Copilot Studio can read, similar to files.

What is MCP?

MCP stands for Model Context Protocol. It's a set of rules that helps Copilot Studio communicate with tools and data in a standardized way.

What does 'validate schemas' mean?

It means checking if the definitions for tools and data are in the correct format that Copilot Studio understands, without using complex data types it doesn't support.

Details

Original description by the author

Generate complete Power Platform custom connector with MCP integration for Copilot Studio - includes schema generation, troubleshooting, and validation

repo: github/awesome-copilot

Popularity

GitHub stars
40k
Ranking position
#5282
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills