<?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/aed6fb30fb684f4eaeae908e3baa62fa&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/aed6fb30fb684f4eaeae908e3baa62fa-76937b7354e130d1.gif</thumbnail_url><duration>1523.339</duration><title>Efficiently Managing Webflow MCP Connections Across Multiple Client Projects</title><description>In this video, I share my approach to using the Webflow MCP flexibly across multiple client projects, especially when they exist in different workspaces. I explain how to manage connections and tokens by organizing projects into separate folders for each client, which allows for easier authentication and avoids conflicts. I also demonstrate how to set up the MCP server using Cloud Code within VSCode, ensuring that each project has its unique configuration. If you find this method beneficial, I encourage you to experiment with these configurations and reach out if you need further assistance.</description></oembed>