New to Claude Skills? Learn how to install them →

github on GitHub

MCP Connector Generator

OfficialFree

Streamline MCP server implementation for Copilot Studio.

by github37.7k stars on github/awesome-copilot
1 views
Updated Aug 10, 2026
Get this skill

Free · Opens the source repo

What MCP Connector Generator does

The MCP Connector Generator is designed to facilitate the creation of custom connectors for the Microsoft Power Platform, specifically optimized for integration with Copilot Studio. This skill automates the generation of a complete Model Context Protocol (MCP) server implementation, ensuring compliance with Power Platform connector standards. It supports JSON-RPC 2.0 communication and provides a streamable HTTP endpoint, making it suitable for developers looking to integrate advanced functionalities into their applications.

By following a structured approach, the generator creates all necessary files, including the API definition, properties, and server code. The output adheres to strict schema compliance requirements, eliminating reference types and ensuring that only single type values are used. This focus on simplicity and clarity helps developers avoid common pitfalls when creating connectors, allowing for a more efficient development process.

The MCP Connector Generator is particularly useful for teams working with Microsoft technologies who need to implement custom solutions that leverage the capabilities of Copilot Studio. It streamlines the process of setting up the server and ensures that all components, such as tools and resources, are correctly defined and accessible. This allows developers to focus on building features rather than wrestling with the intricacies of connector standards.

In summary, this skill is an essential tool for developers aiming to create robust MCP server implementations that integrate seamlessly with Copilot Studio, enhancing their Power Platform projects with minimal effort.

When to use it

Use this skill when you need to quickly generate a compliant MCP server for integration with Copilot Studio.

When not to use it

This skill may not be suitable for projects that require custom features outside the defined MCP standards or for non-Microsoft environments.

What you can build with it

Customer Data Management

Generate an MCP server for managing and analyzing customer data, integrating with CRM APIs.

Real-time Data Processing

Create a server that streams real-time data to and from external APIs, using the MCP protocol.

Custom Tool Development

Quickly set up tools that process specific data types and return structured outputs for use in Power Platform.

How to install MCP Connector Generator

View source

1. Install with the skills CLI

npx skills add github/awesome-copilot/mcp-copilot-studio-server-generator --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by github

Power Platform MCP Connector Generator

Generate a complete Power Platform custom connector with Model Context Protocol (MCP) integration for Microsoft Copilot Studio. This prompt creates all necessary files following Power Platform connector standards with MCP streamable HTTP support.

Instructions

Create a complete MCP server implementation that:

  1. Uses Copilot Studio MCP Pattern:

    • Implement x-ms-agentic-protocol: mcp-streamable-1.0
    • Support JSON-RPC 2.0 communication protocol
    • Provide streamable HTTP endpoint at /mcp
    • Follow Power Platform connector structure
  2. Schema Compliance Requirements:

    • NO reference types in tool inputs/outputs (filtered by Copilot Studio)
    • Single type values only (not arrays of multiple types)
    • Avoid enum inputs (interpreted as string, not enum)
    • Use primitive types: string, number, integer, boolean, array, object
    • Ensure all endpoints return full URIs
  3. MCP Components to Include:

    • Tools: Functions for the language model to call (✅ Supported in Copilot Studio)
    • Resources: File-like data outputs from tools (✅ Supported in Copilot Studio - must be tool outputs to be accessible)
    • Prompts: Predefined templates for specific tasks (❌ Not yet supported in Copilot Studio)
  4. Implementation Structure:

    /apiDefinition.swagger.json  (Power Platform connector schema)
    /apiProperties.json         (Connector metadata and configuration)
    /script.csx                 (Custom code transformations and logic)
    /server/                    (MCP server implementation)
    /tools/                     (Individual MCP tools)
    /resources/                 (MCP resource handlers)
    

Context Variables

  • Server Purpose: [Describe what the MCP server should accomplish]
  • Tools Needed: [List of specific tools to implement]
  • Resources: [Types of resources to provide]
  • Authentication: [Auth method: none, api-key, oauth2]
  • Host Environment: [Azure Function, Express.js, FastAPI, etc.]
  • Target APIs: [External APIs to integrate with]

Expected Output

Generate:

  1. apiDefinition.swagger.json with:

    • Proper x-ms-agentic-protocol: mcp-streamable-1.0
    • MCP endpoint at POST /mcp
    • Compliant schema definitions (no reference types)
    • McpResponse and McpErrorResponse definitions
  2. apiProperties.json with:

    • Connector metadata and branding
    • Authentication configuration
    • Policy templates if needed
  3. script.csx with:

    • Custom C# code for request/response transformations
    • MCP JSON-RPC message handling logic
    • Data validation and processing functions
    • Error handling and logging capabilities
  4. MCP Server Code with:

    • JSON-RPC 2.0 request handler
    • Tool registration and execution
    • Resource management (as tool outputs)
    • Proper error handling
    • Copilot Studio compatibility checks
  5. Individual Tools that:

    • Accept only primitive type inputs
    • Return structured outputs
    • Include resources as outputs when needed
    • Provide clear descriptions for Copilot Studio
  6. Deployment Configuration for:

    • Power Platform environment
    • Copilot Studio agent integration
    • Testing and validation

Validation Checklist

Ensure generated code:

  • No reference types in schemas
  • All type fields are single types
  • Enum handling via string with validation
  • Resources available through tool outputs
  • Full URI endpoints
  • JSON-RPC 2.0 compliance
  • Proper x-ms-agentic-protocol header
  • McpResponse/McpErrorResponse schemas
  • Clear tool descriptions for Copilot Studio
  • Generative Orchestration compatible

Example Usage

Server Purpose: Customer data management and analysis
Tools Needed: 
  - searchCustomers
  - getCustomerDetails
  - analyzeCustomerTrends
Resources:
  - Customer profiles
  - Analysis reports
Authentication: oauth2
Host Environment: Azure Function
Target APIs: CRM System REST API

Frequently asked questions about MCP Connector Generator

Similar skills