Answered

MCP tools not listed in Agent custom connector

(1) Share

Report

Posted on by ES-21071522-0

I was able to successfully add a custom connector for MCP server. When testing it in Power App I am able to send a successful requests and receive back the list of available tools. However, when I try to add this MCP tool to my agent in the Copilot Studio, the list of tools displays "No tools available." I don't see any obvious errors as the network request returns an empty collection and no errors.

MCP connector Swagger configuration:

swagger: '2.0'
info:
  title: REDACTED
  description: MCP Test Specification, YAML for SSE MCP support in Copilot Studio
  version: 1.0.0
host: REDACTED.net
basePath: /
schemes:
  - https
consumes: []
produces: []
paths:
  /mcp:
    post:
      summary: Contoso Lead Management Server
      x-ms-agentic-protocol: mcp-streamable-1.0
      operationId: InvokeServer
      responses:
        '200':
          description: Success
parameters: {}
responses: {}
securityDefinitions:
  api_key:
    type: apiKey
    in: header
    name: api-key
security:
  - api_key: []
tags: []

Testing in Power Apps:

Trying to set it up in Copilot Studio agent (clicking refresh button doesn't help):

Categories:

Model context protocol

I have the same question (2)

All responses (3)

Answers (1)

Michael E. Gernaey 53,479 Super User 2025 Season 2 on at

Like (1)

Report

Hi @ES-21071522-0

I believe one of my other posters helped someone with this. I apologize I am not sure what the issue is so I am only sharing this just in case it helps.

Extend your agent with Model Context Protocol - Microsoft Copilot Studio | Microsoft Learn

I am working on my own custom MCP so hopefully in the next few days I might even have an answer for you that is much more definitive.

If you by chance got it working though it would be great if you can share how.

Thanks!!

Was this reply helpful? Yes No
Verified answer

ES-21071522-0 22 on at

Like (1)

Report

I've got it working using the GitHub provided template when creating a new connector:

- New custom connector

- Import from GitHub

- Connector type: Custom

- Branch: dev

- Connector: MCP-Streamable-HTTP

When in the edit mode, I switched to Swagger editor and updated the generated YAML. The only thing that I changed was the URL and custom headers. I don't know what was different before that didn't make it work.

Was this reply helpful? Yes No
Michael E. Gernaey 53,479 Super User 2025 Season 2 on at

Like (0)

Report

Hi @ES-21071522-0

Thank you for sharing, that is very helpful for future folks having an issue with this!!

Was this reply helpful? Yes No