Connect the Whimsical MCP server to a Microsoft Copilot Studio agent and your agent can create and edit Whimsical files as part of a conversation - flowcharts, mind maps, wireframes, sticky notes, and docs - without anyone leaving Copilot.
Once it's connected, you can ask the agent things like "map out the onboarding flow for the new billing plan" or "turn these meeting notes into a mind map", and it builds the file in Whimsical and returns a link.
https://mcp.whimsical.com/mcpWhimsical now appears in your agent's Tools list, and its actions are available to the agent.
Open the Preview tab and try a prompt such as: "Create a flowchart of a password reset flow: request reset, send email, click link, set new password, confirm."
The agent should return a link to a new Whimsical file. Open it to check the result, then publish the agent when you're happy with it.
Copilot Studio decides which tool to call based on your agent's instructions. If it doesn't reach for Whimsical when you'd expect it to, add a line to the Instructions field, for example:
When the user asks for a diagram, flowchart, mind map, wireframe, or doc, use the Whimsical tools to create it and share the link.
The agent gets the same tools as any other MCP client: searching your workspace, reading files, creating boards, flowcharts, mind maps, sequence diagrams, wireframes, sticky notes, tables, and docs, editing existing files, and reading or leaving comments. See Whimsical MCP - supported tools for the full list and example prompts.
The connection still shows as Not connected. Close and reopen the Select a connection dialog. If it still shows as disconnected, delete the connection and create it again, and check that pop-ups aren't blocked for Copilot Studio.
Files are created in the wrong workspace. Files go to the workspace tied to the account that authorised the connection. Remove the connection and create a new one while signed in to the right Whimsical workspace.
The agent can't find an existing file. The agent only sees files the authorising account can access - the maker's access on a shared connection, each person's own access on an end-user connection.