A collection of Power Platform custom connectors with Model Context Protocol (MCP) integration for Microsoft Copilot Studio agents.
This repository contains custom connectors that operate in dual mode:
- Direct API operations for Power Automate flows and Power Apps
- MCP protocol support for natural language tool invocation in Copilot Studio
All connectors use custom code (C# scripts) to implement both REST API handlers and MCP JSON-RPC 2.0 protocol, eliminating the need for external servers or Azure dependencies.
Microsoft Bookings connector with 30 MCP tools for managing booking businesses, services, staff, customers, and appointments via Microsoft Graph API.
Collection of connector code samples and patterns.
Copilot Studio credits consumption monitoring and licensing management.
Access to Crunchbase company, people, and funding data.
Execute custom Dataverse APIs via Power Platform connector.
49 MCP tools exposing comprehensive Dataverse operations plus orchestration capabilities.
Features:
- 45 Dataverse Web API operations across 11 categories (READ, WRITE, BULK, RELATIONSHIPS, METADATA, etc.)
- 4 orchestration tools for intelligent tool discovery and execution:
discover_functions— Find available tools/resources/promptsinvoke_tool— Trigger a specific toolorchestrate_plan— Coordinate multi-step operationslearn_patterns— Retrieve organizational learning from Dataverse
- Dynamic tool loading from Dataverse table (
tst_agentinstructions) - Self-learning pattern recognition and storage
- OAuth 2.0 authentication with Microsoft Dataverse
Microsoft Graph Calendar operations with MCP support for Copilot Studio agents.
File hash computation and verification for Microsoft Graph files with 4 MCP tools.
Features:
- QuickXorHash algorithm (OneDrive/SharePoint standard)
- SHA1 and CRC32 hash computation
- File integrity verification against Microsoft Graph stored hashes
- Change detection and deduplication
Microsoft Graph Mail operations for email management via Power Platform.
Microsoft Places API integration for workspace and location management.
Comprehensive user profile, organizational hierarchy, presence, and people discovery with 25 MCP tools. Enhanced alternative to Microsoft's first-party User Profile MCP Server.
SharePoint Embedded container and content management.
Snowflake data warehouse connector for Power Platform.
Each connector follows this pattern:
connector-folder/
├── apiDefinition.swagger.json # OpenAPI 2.0 with x-ms-* extensions
├── apiProperties.json # Marks operations using scriptOperations
├── script.csx # C# (.NET Standard 2.0) dual-mode handler
└── readme.md # Documentation
script.csx routes requests by path:
/mcpendpoint → MCP JSON-RPC 2.0 protocol (initialize,tools/list,tools/call)/operationendpoints → Direct REST API for Power Automate/Power Apps
Connectors marked with "x-ms-agentic-protocol": "mcp-streamable-1.0" in OpenAPI definitions expose:
- tools/list — Returns available MCP tools with descriptions and JSON schemas
- tools/call — Executes tools by name with natural language arguments
- initialize — Capability negotiation with Copilot Studio
- Power Platform environment
- Appropriate Microsoft 365 licenses
- Microsoft Graph API permissions (varies by connector)
- Power Automate or Copilot Studio license
- Navigate to Power Platform maker portal
- Select target environment
- Data → Custom connectors → New custom connector → Import an OpenAPI file
- Upload
apiDefinition.swagger.jsonfrom connector folder - On Code tab, enable custom code
- Paste contents of
script.csx - Create connector
- Test connection with OAuth flow
Add connector actions to flows like any other connector. Operations appear as standard actions with IntelliSense support.
- Add connector to your Copilot Studio environment
- Create connection with appropriate permissions
- Enable actions in agent's knowledge sources
- Agent automatically discovers and invokes tools based on natural language
All connectors use Microsoft Orange Red (#da3b01) as the brand color in apiProperties.json.
- OAuth 2.0 with Microsoft Entra ID (Azure AD)
- Scopes vary by connector (Graph API, Dataverse, etc.)
- No API keys or connection strings required
- Power Platform execution limits — 5-10 second timeout for connector operations
- File size limits — Base64 encoding overhead, typically 50 MB max
- Read-only where applicable — Some connectors don't support write operations
- Graph API rate limits — Standard Microsoft Graph throttling applies
# Install Power Platform CLI
paconn login # Device code flow
# Validate connector
cd connector-folder
paconn validate --api-def apiDefinition.swagger.jsonConnectors cannot run locally. Deploy to Power Platform and test via:
- Flow action tester in Power Automate
- "Test" tab in connector designer
- Copilot Studio agent conversations
This repository represents production connectors in use. Contributions welcome for:
- Bug fixes
- Documentation improvements
- New MCP tool suggestions
- Performance optimizations
MIT License - see individual connector folders for specific licensing details.
Developer: Troy Taylor
Email: troytaylor@microsoft.com
Organization: Microsoft
- Power Platform Custom Connectors
- Model Context Protocol Specification
- Microsoft Graph API
- Copilot Studio Documentation
- Power Automate Connector Development
⭐ Star this repo if you find these connectors useful!