Connectors issue

(0) Share

Report

Posted on by Tulsiram Methre

Hi Folks,

I am developing an agent and have these two MCP details, but my connectors cannot connect to them and return 500 errors along with many other issues. Could someone please assist?

For your information, the credentials have been changed for security reasons. The main objective is to create two connectors that can retrieve the tools list and handle user queries, providing responses with the data so that business users can also understand what is happening.

{
"servers": {
"SOC-MCP-Gateway": {
"url": "https://regasn-iad1sa0.api.sacs.splunk.com/system/mcp-gateway/v1/",
"type": "http",
"headers": {
"X-SF-REALM": "usdsds",
"X-SF-TOKEN": "20sdsdskzUsVXQ"
}
},
"SE-PROD-MCP": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://splunk-search-rest.sass.glbas.prod.rsatg.aaswsspgi/services/mcp",
"--header",
"Authorization: Bearer cd2JdZQgDd0QF7gPkB9TxbZNjtu/tqxA0JMPzs4biJ+9IrKK+5E4Wy4Z86dO91NpI5usdsdsdsdsdNnVtZOQ0Fw03iMLATpPsdsdsdsd"
]
}
}
}

Categories:

Model context protocol

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

11manish 3,749 on at

Like
a
(0)

Report
Copy link

Link copied!
A 500 Internal Server Error typically indicates that the request reached the MCP server, but the server failed to process it. Based on your configuration, the issue is more likely related to the MCP server, gateway, or authentication than Copilot Studio.

Key points to check:

Test the MCP endpoint using Postman or curl to confirm whether the issue exists outside Copilot Studio.

Verify all required authentication headers (Authorization, X-SF-TOKEN, X-SF-REALM) are correct and valid.

Ensure the MCP server exposes a standard HTTP(S) endpoint. Copilot Studio does not support npx mcp-remote or other local command-based MCP clients.

Confirm the MCP server correctly implements tool discovery and tool execution endpoints.

Review the MCP server/gateway logs for the root cause of the HTTP 500 error.

Check for firewall, proxy, TLS, or network restrictions that could affect connectivity.

If the HTTP endpoint still returns a 500 after these checks, the issue is most likely on the MCP server side and should be investigated by the server owner using the server logs and request details.

Was this reply helpful? Yes No
Tulsiram Methre 2 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi Manish,

Thank you for the detailed response. Your guidance helped me separate the Copilot Studio connector issue from the MCP server and transport configuration.

I have now successfully connected the SOC MCP Gateway to Copilot Studio using the native Model Context Protocol option.

The SOC endpoint is working as a Streamable HTTP MCP server, and Copilot Studio is now dynamically discovering the individual o11y_* tools. The tools can be enabled individually and are no longer displayed as one generic connector action.

The working connector configuration uses:

Streamable HTTP transport A single POST operation x-ms-agentic-protocol: mcp-streamable-1.0 X-SF-REALM X-SF-TOKEN Content-Type: application/json Accept: application/json, text/event-stream

One important point I found was that the MCP connector definition should not explicitly add a request body. Copilot Studio/Power Platform generates its own MCP request body internally. Adding another in: body parameter caused the OpenAPI validation error: “Operation can have only one body parameter.”

The SOC MCP tools are now visible and working. The Resources (Preview) section still shows “No resources available / Connector request failed,” but the server appears to expose MCP tools rather than a resource catalogue, so that seems separate from tool discovery and execution.

My remaining issue is with the SE MCP server. The configuration supplied to me currently uses:

npx mcp-remote <SE MCP endpoint> Authorization: Bearer <token>

Based on your response, I understand that Copilot Studio cannot execute npx mcp-remote, because that is a local command-based client configuration.

Could you please advise on the following?

If the underlying SE /services/mcp endpoint already implements native Streamable HTTP, can I connect Copilot Studio directly to that URL and remove npx and mcp-remote?

Can the Copilot Studio MCP onboarding wizard use an API key configured with the header name Authorization, where the connection value is entered as Bearer <token>?

If Copilot Studio’s API-key connection does not preserve the Bearer prefix correctly, should this be handled using a custom MCP connector or a request-header policy?

If the SE endpoint depends on mcp-remote for protocol translation, does that mean we need to deploy an externally reachable Streamable HTTP MCP proxy or gateway in front of it?

What is the best way to verify whether the SE endpoint itself supports Streamable HTTP—should a JSON-RPC initialize POST request directly to the endpoint return the MCP server capabilities?

The SOC portion is resolved. I am mainly trying to determine whether the SE endpoint is already directly compatible with Copilot Studio or whether mcp-remote is currently providing a required transport/protocol bridge.

Thanks again for pointing me in the right direction.

Was this reply helpful? Yes No