MCP Copilot Studio Server Generator

Power Platform MCP connector generator

Generate a Microsoft Copilot Studio-compatible MCP implementation by combining a streamable HTTP MCP server with Power Platform custom connector files and schemas that avoid constructs Copilot Studio filters or misinterprets.

When to invoke

• "Generate a Power Platform MCP connector."
• "Create an MCP server for Copilot Studio."
• "Build a custom connector with x-ms-agentic-protocol."
• "Scaffold apiDefinition.swagger.json, apiProperties.json, and script.csx for MCP."
• "Make my MCP tools compatible with Microsoft Copilot Studio."

Inputs

Use $ARGUMENTS as the server purpose, target API, or tool list when provided. If details are missing, collect them before generating files.

Copilot Studio MCP pattern

Schema compliance requirements

Generated file 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)

MCP component rules

Validation checklist

• No reference types in schemas.
• All type fields are single types.
• Enum handling uses string with validation.
• Resources are available through tool outputs.
• Endpoints return full URIs.
• JSON-RPC 2.0 compliance is implemented.
• x-ms-agentic-protocol: mcp-streamable-1.0 is present.
• McpResponse and McpErrorResponse schemas are defined.
• Tool descriptions are clear for Copilot Studio.
• Generative Orchestration compatibility is checked.

Example input

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

Gotchas

• Do not use $ref for tool payloads: Copilot Studio can filter reference types and make the tool unusable.
• Do not model enum inputs as OpenAPI enums: write string with validation and a description of accepted values.
• Do not expose resources only through MCP resource APIs: return them through tool outputs for Copilot Studio.
• Do not promise prompt support in Copilot Studio: prompts may exist in the MCP server but are not yet a Copilot Studio integration surface.

Output template

## Copilot Studio MCP connector

**Status:** generated | requirements needed | blocked
**Server purpose:** <purpose>
**Host environment:** Azure Function | Express.js | FastAPI | other
**Authentication:** none | api-key | oauth2

### Files
| Path | Purpose |
| --- | --- |
| `apiDefinition.swagger.json` | Connector schema with POST `/mcp` and `x-ms-agentic-protocol: mcp-streamable-1.0` |
| `apiProperties.json` | Connector metadata and authentication |
| `script.csx` | Custom transformations and JSON-RPC handling |
| `server/` | MCP server implementation |
| `tools/` | Individual MCP tools |
| `resources/` | Resource handlers exposed through tool outputs |

### Tools
| Tool | Inputs | Output | Copilot Studio notes |
| --- | --- | --- | --- |
| `searchCustomers` | primitive schema | structured object | no `$ref`, no enum inputs |

### Validation
- No reference types: pass | fail
- Single type fields: pass | fail
- JSON-RPC 2.0: pass | fail
- `McpResponse` / `McpErrorResponse`: pass | fail

Quality gate

• Server Purpose, Tools Needed, Resources, Authentication, Host Environment, and Target APIs are known or explicitly marked not applicable.
• apiDefinition.swagger.json, apiProperties.json, script.csx, server/, tools/, and resources/ are generated when requested.
• POST /mcp uses streamable HTTP and JSON-RPC 2.0.
• x-ms-agentic-protocol: mcp-streamable-1.0 appears in the connector definition.
• Tool input/output schemas avoid reference types, multi-type values, and enum inputs.
• McpResponse and McpErrorResponse are present.
• Resources are surfaced as tool outputs and prompts are labeled as not yet supported in Copilot Studio.
• All endpoints return full URIs and tool descriptions are clear for Generative Orchestration.