Skip to main content

Notifications

Announcements

Welcome to the Power Platform Communities
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Copilot Studio - Model Context Protocol / Welcome to the Copilot...
Copilot Studio - Model Context Protocol
Unanswered

Welcome to the Copilot Studio Model Context Protocol community

(22) ShareShare
ReportReport
Posted on by zankard Moderator

Welcome to the Copilot Studio Model Context Protocol community. This forum is dedicated to all things related to MCP Support in Copilot Studio where you can connect with fellow users, share insights, and explore innovative ways to leverage this capability. 

Want to know more about our public preview announcement? Check it out here: https://aka.ms/mcsmcp

Ask questions, share your stories, and dive into the conversation. Feel free to share any feedback, suggestions, or issues you're facing – we're here to help and eager to hear from you!

Thank you for being part of our community. We look forward to your contributions!"

 

  • CU08072022-0 Profile Picture
    CU08072022-0 4 on at
    Welcome to the Copilot Studio Model Context Protocol community
    MCP Plugin Architecture Recap
     
    ComponentRequired
     
    Azure FunctionDeployed and accepting traffic
    MCP Server TriggerEnabled and returning valid JSON-RPC
    OpenAPI Plugin (YAML)Proper servers: URL + schema
    Copilot StudioLoads plugin and triggers tools
     
    {
      "jsonrpc": "2.0",
      "id": "abc123",
      "method": "tool",
      "params": { "question": "..." }
    }
     
     
    openapi: 3.0.1
    info:
      title: ZakatEligibilityTool
      version: 1.0.0
    servers:
      - url: https://zakatai.azurewebsites.net
    paths:
      /api/zakatquery:
        post:
          operationId: zakatEligibility
          requestBody:
            required: true
            content:
              application/json:
                schema:
                  type: object
                  properties:
                    question:
                      type: string
          responses:
            '200':
              description: OK
              content:
                application/json:
                  schema:
                    type: object
                    properties:
                      answer:
                        type: stringopenapi: 3.0.1
    info:
      title: ZakatEligibilityTool
      version: 1.0.0
    servers:
      - url: https://zakatai.azurewebsites.net
    paths:
      /api/zakatquery:
        post:
          operationId: zakatEligibility
          requestBody:
            required: true
            content:
              application/json:
                schema:
                  type: object
                  properties:
                    question:
                      type: string
          responses:
            '200':
              description: OK
              content:
                application/json:
                  schema:
                    type: object
                    properties:
                      answer:
                        type:string 
    {
      "jsonrpc": "2.0",
      "id": "abc123",
      "result": {
        "answer": "Zakat applies if your Nisab threshold is met."
      }
    }
  • Suggested answer
    CU08072022-0 Profile Picture
    CU08072022-0 4 on at
    Welcome to the Copilot Studio Model Context Protocol community
    Be. 
    **Use Case**: I am developing a Zakat eligibility Copilot for Hijra Bank using Copilot Studio + Azure Functions (MCP).
    **Problem**: The plugin loads, but no response is returned when the Copilot sends a prompt. Function returns JSON-RPC as expected.
    **Endpoint tested**: https://zakatai.azurewebsites.net/api/zakatquery
    **YAML plugin format**: OpenAPI 3.0.1, with full HTTPS URL in `servers:` block.
    Any insights on whether streaming or function key configurations affect plugin response?
  • MN-22041403-0 Profile Picture
    MN-22041403-0 2 on at
    Welcome to the Copilot Studio Model Context Protocol community
    Hi zankard.
    Thank you for replying.
    I would need some clarifications about some of the comments you made:
     
    1- I take it Copilot Studio isn't quite ready to handle incoming SSE streams ?
    2- Assuming the answer to (1) is 'yes' , what endpoints should be exposed in the YAML file ?(see attached the  YAML file I constructed for my custom M365 connector)
    3- The MCP client , in theory, should receive an incoming SSE stream , keep the session alive and redirect to the correct endpoint that the MCP server exposes.
        If I now need to expose each endpoint , we are really missing on the entire idea here ?
    4- My MCP Server is actually a deployed(remote) Azure Function that has multiple MCP triggers , it is 'Anonymous' so it accepts inbound traffic and when tested via my local .NET app ( that uses Semantic Kernel to instantiate   the MCP client )- it works well!
    5- When I try to access the endpoint https://<function_app_name>./runtime/webhooks/mcp/sse?code='<function_key>' I get the stream:
    event: endpoint
data: message?azmcpcs=3RotbC1KjRJxvzoEECbWKG1olHa4xKibcikCv5Hn7YGo_EEKm6wNUJfP3BAwF8XOZu-zFD7byZtIaZx0CWjUfOcdjiq6Lny8YiimnX13t7qCZxPNTAH-UTr33nIPhm8Md6b5j5VaoqQ2LtPD-ziRkWea9-7wfMDzNVDevuKc9jPhq96Zvg&code=2umPz1y8qGq3MA02qWhj3IKswsiV5QY8XwKr4DPQNDMHAzFuAjZ_Yw==

data: {"jsonrpc":"2.0","id":"c722d09d-e000-42ca-bc15-c5b2275567d1-1","method":"ping"}

data: {"jsonrpc":"2.0","id":"c722d09d-e000-42ca-bc15-c5b2275567d1-2","method":"ping"}
    6- You say Copilot Studio needs to have a fully qualified URL , so I wrapped it with APIM and created inbound and outbound policies to generate the following :
    event: endpoint
data: https://apim-erpure.azure-api.net/mcp/runtime/webhooks/mcp/message?azmcpcs=l_xZI2d2poXQ5LSlbI-lDhMMW5m3nPhRiFKsnU9LOR4md4S9QqgZyj7IA66ajWlqJA6Z6D4dlXljNc8zIumdCUL0tHjLdX8Fj-QozjQKX6sh_QtrRboXVYvvtFmADZnCiBo7MZm7ogoXPsTPolVS3ZJmM19B3ef2e9quK3sb9MEBS6nYAQ&code=bXwTHRHdZT33v1aEAsDjcVaP4VK_gpYiaOCZIsrfdIxGAzFu4TAPTA==
    However , nothing works when I try to setup the connector and plug it in to Copilot Studio- everything either freezes or the connector could not be added(I can click on it for hours and nothing happens).
     
    I think we need to jump into a session in order to debug this and see what needs to be done to resolve this.
    Much have been said on the MCP capabilities but the only clients I have seen so far that are able to consume it properly are either Claude desktop or VS Code.
    Hopefully we can get it solved
    Thanks !
    mcp_apim.yaml
  • zankard Profile Picture
    zankard Moderator on at
    Welcome to the Copilot Studio Model Context Protocol community
     
    Thanks for reaching out! Please make sure you that your endpoint returned in the open SSE connection call is a fully qualified URL. See https://aka.ms/mcsmcpdocs for the latest information on Known Issues. 
     
    For example:
    By default, most standard SDK configurations return something like this:
     
    event: endpoint
    data: /message 

    But, Copilot Studio requires a fully qualified URI:

    event: endpoint
    data: https://microsoft.com/mcp/message

    We are actively working to remove this limitation, as well as support for the Streamable Transport, to simplify this communication pattern. 

    Let us know if this helps resolve your issue! 

  • CU08042207-0 Profile Picture
    CU08042207-0 2 on at
    Welcome to the Copilot Studio Model Context Protocol community

    Hello,

    First off, this is a fantastic and much-needed initiative—kudos to the team!

    That said, I may be misunderstanding how the MCP feature in Copilot Studio is intended to work, or perhaps it's not functioning as expected in my case.

    I’ve successfully created and deployed an MCP server as an Azure Function, complete with MCP tool endpoints. Everything works flawlessly when I test it via the MCP Inspector tool.

    However, when I create a custom connector using the OpenAPI YAML (which could benefit from further clarification), and then try to use it as an action in Copilot Studio, the entire flow seems to freeze—nothing gets triggered or invoked.

    I’ve gone through the checklist: validated IAM roles, adjusted CORS settings, and ensured the function app is running—but still no luck.

    My expectation is that once the MCP connector is loaded into Copilot Studio, and the Azure Function is live, it should be able to invoke the appropriate MCP tool as needed.

    Could I please get some guidance on this?

    Thanks so much!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Welcome to the Power Platform Communities

Quick Links

Paul Stork – Community Spotlight

We are honored to recognize Paul Stork as our July 2025 Community…

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard > Copilot Studio

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 169 Super User 2025 Season 1

#2
Romain The Low-Code Bearded Bear Profile Picture

Romain The Low-Code... 150

#3
sandeep_angara Profile Picture

sandeep_angara 75

Last month Overall leaderboard

Featured topics

Announcing the "Microsoft Copilot Studio ❤️ MCP" lab

Product updates

Microsoft Power Platform Community release plans