mcp-copilot-studio-server-generator
Generate a complete MCP server implementation optimized for Copilot Studio integration with proper schema constraints and streamable HTTP support
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 4.1w
- Forks
- 5.3k
01 前言 Front Matter
- name
- mcp-copilot-studio-server-generator
- description
- Generate a complete MCP server implementation optimized for Copilot Studio integration with proper schema constraints and streamable HTTP support
02 资源文件 3
- 参考文档AGENT-BRIEF.md7.8 KB
- 参考文档agents/openai.yaml135 B
- 参考文档OUT-OF-SCOPE.md4.6 KB
03 SKILL.md 正文
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:
-
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
- Implement
-
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
-
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)
-
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:
-
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
- Proper
-
apiProperties.json with:
- Connector metadata and branding
- Authentication configuration
- Policy templates if needed
-
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
-
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
-
Individual Tools that:
- Accept only primitive type inputs
- Return structured outputs
- Include resources as outputs when needed
- Provide clear descriptions for Copilot Studio
-
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
04 同仓库更多 Skills
supabase-rls-policies
Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.
skill-distribution-audit
Audit a skill collection before release or investigate installer omissions, archived/template leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.
logicapps-custom-code-net10-migration
Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project/package configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.
winmd-api-search
Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI/ML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).
resemble-detect
Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI
quality-playbook
Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.