Mcp Copilot Studio Server Generator
Generate a Copilot Studio–ready MCP server and Power Platform custom connector with streamable HTTP and schema constraints enforced.
Overview
MCP Copilot Studio Server Generator is an agent skill for the Build phase that produces an MCP streamable HTTP server and Power Platform connector package tuned for Microsoft Copilot Studio schema limits.
Install
npx skills add https://github.com/github/awesome-copilot --skill mcp-copilot-studio-server-generatorWhat is this skill?
- Implements x-ms-agentic-protocol mcp-streamable-1.0 with JSON-RPC 2.0 on /mcp
- Enforces Copilot Studio schema rules: no reference types, single primitive types, avoid enum inputs
- Generates Tools and Resources aligned with what Copilot Studio exposes (Prompts noted as unsupported)
- Power Platform custom connector file structure included
- Streamable HTTP endpoint pattern for agentic protocol compliance
- MCP Tools and Resources marked supported; Prompts marked not yet supported in Copilot Studio per skill doc
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 want Copilot Studio to call your MCP tools but keep hitting rejected connectors due to reference types, enums, or non-compliant agentic protocol headers.
Who is it for?
Builders integrating custom backends into Copilot Studio who need MCP-compliant stubs without manually reverse-engineering Microsoft schema filters.
Skip if: Generic MCP servers for Claude Desktop only, or projects that do not target Power Platform / Copilot Studio import rules.
When should I use this skill?
You need a complete MCP server implementation optimized for Copilot Studio with streamable HTTP and connector-compliant schemas.
What do I get? / Deliverables
You receive generated MCP server and custom connector files with JSON-RPC streamable HTTP on /mcp and tool schemas Copilot Studio can accept.
- MCP server implementation skeleton
- Power Platform custom connector definitions
- Tool and resource schemas without reference types
Recommended Skills
Journey fit
Custom connectors and MCP endpoints are built artifacts that wire Copilot Studio to your tools before ship and operate. MCP over streamable HTTP is an integration pattern between agent hosts and your backend, not UI or docs work.
How it compares
Skill-packaged generator for Copilot Studio connectors—not a hosted MCP marketplace listing or a no-code-only Power Automate flow.
Common Questions / FAQ
Who is mcp-copilot-studio-server-generator for?
Indie and solo developers building Power Platform custom connectors that expose MCP tools to Microsoft Copilot Studio.
When should I use mcp-copilot-studio-server-generator?
During Build while designing agent integrations—after you know your tool surface but before you deploy the HTTP endpoint to a host Copilot Studio can reach.
Is mcp-copilot-studio-server-generator safe to install?
Generated servers often need network and secrets at runtime; review Security Audits on this Prism page and audit generated code before production credentials.
SKILL.md
READMESKILL.md - Mcp Copilot Studio Server Generator
# 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 ```yaml Server Purpose: Customer data man