<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/a38bbc37964047c2a1231c1c1efd377b&quot; frameborder=&quot;0&quot; width=&quot;1110&quot; height=&quot;832&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>832</height><width>1110</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>832</thumbnail_height><thumbnail_width>1110</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/a38bbc37964047c2a1231c1c1efd377b-643fe9f2815e862f.gif</thumbnail_url><duration>228.6361</duration><title>Debugging Microsoft Copilot Studio Integration with Python MCP Servers 🛠️</title><description>In this video, I demonstrate an issue with the integration of Microsoft Copilot Studio and Python-based MCP servers. I set up a local MCP server and a proxy to inspect traffic, revealing that a critical follow-up request from Microsoft is missing due to the ID field being incorrectly formatted as a number instead of a string. By modifying the ID to a string, I show that the flow continues successfully, resulting in three messages being exchanged. I encourage viewers to consider this ID formatting issue when troubleshooting similar integration problems. Please let me know if you have any questions or need further clarification on this matter.</description></oembed>