Getting error, while trying to connect to Microsoft Docs MCP Server from MCP Client with Streamable HTTP

[anushav2002]

Getting this error - "Error POSTing to endpoint (HTTP 500): The key {83e8a517-600e-4af6-a325-99004cd1aa07} was not found in the key ring. For more information go to https://aka.ms/aspnet/dataprotectionwarning" while trying to connect to Microsoft Docs MCP Server with Streamable HTTP. Kindly, let me know whether any key related information need to be given from MCP Client side to connect to the server.

[pdebruin]

Hi @anushav2002, thank you for reaching out.

Docs MCP doesn't require authentication at this point. You only need to configure the MCP Server's url. Try for yourself using GitHub Copilot in VS Code, or mcp inspector https://modelcontextprotocol.io/docs/tools/inspector.

Feel free to share details of your environment and solution too, if you want us to think along.

Hope that helps 🙂

[anushav2002]

Thank you @pdebruin for your response,

I have used the streamable HTTP as type to connect my client with Microsoft Docs server. At first I got this error - "Error POSTing to endpoint (HTTP 500): The key {83e8a517-600e-4af6-a325-99004cd1aa07} was not found in the key ring. For more information go to https://aka.ms/aspnet/dataprotectionwarning" and server not connected.

Next, again I have tried to reach the Microsoft Docs server. At that time, server got connected and tools listing and tools calling happened. But after 3mins, server got disconnected and tool call failed. After this step, I could not reach the Microsoft Docs server and facing the same issue.

I have also tried out with sse type, got the sse error: 405 issue. As you told, I have tried to access the Microsoft Docs server in Github Co-pilot and server got connected and tool calling process happened correctly. Kindly, please let me know is there any difference between http and streamable-http? In Github Co-pilot we use http type to configure.

I hope both http and streamable-http type are same. Please let me know is anyother http protocol is followed to connect the server. Kindly, please provide me with the steps or help documentations that are available to connect to Microsoft Docs Server.

[pdebruin]

I understand you are running into challenges. Can you please share details of your environment and solution? Or detailed steps how to reproduce?
Feel free to send me an email (my github alias at hotmail dot com) or find me on LinkedIn if that is more comfortable for sharing sensitive details.

[anushav2002]

Thank you @pdebruin for your response. I could not share those environment details or solution outside. I am using streamable-http type and using @modelcontextprotocol node module for connecting streamble-http transport to communicate with mcp server. I hope you understand the situation, with these information any steps can be provided.

Also, I have an doubt I have tried to connect MCP Inspector. In that, logging level tab - I got the same error, which I have mentioned before. So, kindly let me know the steps to identify the problem. Because, Endpoints are correct and it got connected twice while I am trying, then after that I am facing the same issue.

[TianqiZhang]

@anushav2002 I wonder if it has something to do with network, similar to this case: #5

[anushav2002]

Thank you @TianqiZhang for your response. The issue, which you shared shows, that there might be proxy related issue while accessing the Microsoft Docs Server. But As mentioned in the previous comment, only url of the server is enough to connect with client and has no authentication process.

[partychen]

@anushav2002 Thanks for checking! I’ve tested it multiple times using MCP Inspector, and it works correctly every time — even when the session ID changes. This is expected, since our MCP service is stateless.

If you're still seeing the issue, could you kindly share a short video showing how you’re using it and where it fails?

[partychen]

@anushav2002 We're planning to close this comment as the bug has been fixed. You can refer to this issue for more details.

If you have any further questions or concerns, please feel free to let us know!