Automated summary
Generates a complete Power Platform custom connector plus an MCP server using streamable HTTP and JSON-RPC 2.0, shaped to Microsoft Copilot Studio's constraints.
Strengths
- Bakes in Copilot Studio's schema restrictions from the start: no reference types, single type values only, enums handled as validated strings
- Produces the full expected file set: apiDefinition.swagger.json, apiProperties.json, script.csx, MCP server code, tools and resource handlers
- Ships a detailed validation checklist and guidance for deploying into a Copilot Studio agent
- Clearly separates supported MCP primitives (tools, resources surfaced as tool outputs) from unsupported ones (prompts)
Limitations
- It is a prompt template: context variables such as tools, auth method and host environment must be filled in by hand first
- Tightly scoped to Copilot Studio and Power Platform connector rules, so it is a poor fit for a generic MCP server
- Validation is a static checklist with no execution or real testing of the generated connector
Use it when you need to expose an API to Copilot Studio as MCP tools through a Power Platform custom connector.
Avoid it when building an MCP server for Claude Desktop or another client that does not go through Power Platform connector constraints.
Security analysis
SafeThis is a documentation/code-generation prompt for creating an MCP server connector. It contains no destructive commands, credential exfiltration, obfuscated payloads, or instructions to disable safety controls. Generated code would need normal review, but the skill itself has no meaningful execution risk.
No concerns found
How this analysis is madeExamples
Generate an MCP server and Power Platform custom connector for Copilot Studio that exposes customer data. Tools: get_customer_by_id, search_customers, list_recent_orders. Auth: api-key. Host: Azure Function.Create a Copilot Studio MCP server with JSON-RPC 2.0 over streamable HTTP for a helpdesk API. Tools: create_ticket, update_ticket_status, fetch_ticket. Expose attachments as MCP resources through tool outputs. Auth: oauth2.Review my apiDefinition.swagger.json for Copilot Studio compliance: check for reference types, array-valued type fields, enum inputs, and that the MCP endpoint is POST /mcp with x-ms-agentic-protocol set to mcp-streamable-1.0.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'
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
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/mcp-server-generator-for-copilot-studio-msh3utf5/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/mcp-server-generator-for-copilot-studio-msh3utf5' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/mcp-server-generator-for-copilot-studio-msh3utf5/download' --output '.skill-downloads/mcp-server-generator-for-copilot-studio-msh3utf5/SKILL.md.part' && mv '.skill-downloads/mcp-server-generator-for-copilot-studio-msh3utf5/SKILL.md.part' '.skill-downloads/mcp-server-generator-for-copilot-studio-msh3utf5/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/mcp-server-generator-for-copilot-studio-msh3utf5/SKILL.md' && test -s '.skill-downloads/mcp-server-generator-for-copilot-studio-msh3utf5/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/mcp-copilot-studio-server-generator' && cp -R '.skill-downloads/mcp-server-generator-for-copilot-studio-msh3utf5' '.claude/skills/mcp-copilot-studio-server-generator'Cursor
test -f '.skill-downloads/mcp-server-generator-for-copilot-studio-msh3utf5/SKILL.md' && test -s '.skill-downloads/mcp-server-generator-for-copilot-studio-msh3utf5/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/mcp-copilot-studio-server-generator' && cp -R '.skill-downloads/mcp-server-generator-for-copilot-studio-msh3utf5' '.cursor/skills/mcp-copilot-studio-server-generator'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/mcp-server-generator-for-copilot-studio-msh3utf5'openskills read 'mcp-server-generator-for-copilot-studio-msh3utf5'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/mcp-server-generator-for-copilot-studio-msh3utf5/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.