mcp-copilot-studio-server-generator
Generate a complete MCP server implementation optimized for Copilot Studio integration with proper schema constraints and streamable HTTP support
What this skill does
# 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 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 ```
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.