Cannot connect to a MCP Server

(2) Share

Report

Posted on by TS-09060606-0

Hi all,

I need some support for connecting to my MCP Server:

What's working

1. My MCP Server is working on Claude Desktop, below is the json configuration from Claude:

2. the messages/session_id endpoint is working

What's not working

1. PowerApp Custom Connecting Test keeps spinning:

2. Not responding when adding the tool to my agent

What's unique on my MCP Server

My MCP SSE Server require x_api_key authentication.

Below is my swagger definition

swagger: '2.0'
info:
title: My MCP
description: Custom connector for MCP Server using SSE endpoint
version: 1.0.0
host: mymcp.dev.mycompany.com
basePath: /mcp/my_mcp_instance
schemes:
- https
consumes:
- application/json
paths:
/sse:
get:
summary: Connect to MCP SSE Stream
x-ms-agentic-protocol: mcp-sse-1.0
description: Initiates a connection to the MCP SSE stream.
parameters:
- in: query
name: session_id
type: string
required: false
produces:
- application/json
responses:
'200':
description: Immediate Response
schema:
type: string
'201':
description: Created and will follow callback
operationId: InvokeMCP
tags:
- Agentic
- McpSse
securityDefinitions:
api_key:
type: apiKey
in: header
name: x_api_key
definitions: {}
security:
- api_key: []

What I don't understand

1. Why do I need session_id as a parameter? Since session_id is automatically generated when visiting /sse/ endpoint.

2. What is "x-ms-agentic-protocol" for? I have a mixed response from different websites whether this is required or not.

Many Thanks in advance

Categories:

Model context protocol

I have the same question (1)

All responses (5)

Answers (0)

TS-09060606-0 12 on at

Like (0)

Report

I am now managed to "move forward" a little, however, I am still not able to see my tools and there is an error that I am unsure if it is related, anyone can direct me a little what am I doing wrong?

So now when I am in the Tool Page, I cannot see the tools listed (is this normal?)

In PowerApp, I get this error even though I get Status 200:

Was this reply helpful? Yes No
FW-24061242-0 26 on at

Like (0)

Report

Did you write your server in python? This might be the issue.
The problem is that python sends an integer "id" in the protocol messages,
while MS expects a string.
Hopefully MS fixes this soon.

Was this reply helpful? Yes No
Samrat Gavale Microsoft Employee on at

Like (0)

Report

The x-ms-agentic protocol tag allows the service to add hidden POST action to your connector which is used by agent to post any data to your MCP server. But currently, that change is rolling out and you will have to manually configure two things for the connector to work correctly:

1. Add the POST action in your swagger. See https://gist.github.com/samrat-gavale/0fa11432ce845833378e2deeea5b82f1

2. Add a "route request" policy targeting that POST action. Copilot runtime uses that policy to send payload to appropriate endpoint on the same MCP server, since we don't know that payload receiving endpoint in MCP server beforehand.

Was this reply helpful? Yes No
TS-09060606-0 12 on at

Like (0)

Report

@FW-24061242-0 Yes, I wrote the service in Python, is that means all Python based MCP Servers are not able to run on PowerApps and Copilot Studio now?

Was this reply helpful? Yes No
TS-09060606-0 12 on at

Like (0)

Report

@Samrat Gavale, thanks for the new swagger definition, but unfortunately, tested on my environment, still failed to retrieve the MCP tools.

Was this reply helpful? Yes No