Adobe for creativity
Edit photos, cut video and design from templates via an AI agent.
Create flowcharts, mind maps, wireframes and docs in your Whimsical workspace.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Whimsical MCP server connects your Whimsical workspace to Claude, ChatGPT, Cursor and any MCP-compatible agent. It reads and writes real files in that workspace: searching boards and docs, creating flowcharts, mind maps, wireframes and tables, editing objects on an existing canvas, and deleting files to the trash. Sign-in is OAuth with your Whimsical account.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Yes. Whimsical's supported-tools documentation lists a delete tool that removes a board, doc, folder or diagram, or specific objects inside a board. Anthropic's directory listing omits it entirely. Whimsical states deleted files move to the trash rather than disappearing, and the trash keeps them until you restore or permanently delete them yourself.
Seven. Whimsical's documentation names flowchart, mindmap, sequence_diagram, wireframe, board, sticky_notes and table as supported types on the create tool. The type is an argument rather than a separate tool, so one tool name covers seven different resources. Diagram types are laid out automatically and boards give full positional control.
It patches. Whimsical documents edit as adding, updating or deleting individual objects on an existing board or doc, plus find-and-replace across a diagram. There is no documented replace-whole-file operation on the remote server, so an edit call changes the objects it names rather than emptying the file around them.
No documented tool does that. Whimsical's remote MCP tool list covers search, read, create, edit, layout, delete and comments, with no sharing or permissions tool among them. Link sharing is set in the Share menu in the Whimsical app, which the sharing FAQ describes as off by default for private files until you enable it.
Whimsical's MCP documentation names only an account, with no plan named as a prerequisite. Plan limits still bite through the product: Whimsical's pricing page caps the Free plan at three team boards, and only paid plans allow comment or edit access on public share links. Creating files through MCP consumes the same board allowance.
In your workspace, in whichever section the call targets. Whimsical's sharing documentation says files under Private are private to you by default until you share them, while a team section is visible to that team's members. The file_tree tool browses that hierarchy, so an agent can be pointed at a specific folder before creating anything.
The server advertises separable scopes. Whimsical's OAuth metadata publishes mcp:read and mcp:write as distinct values alongside profile, so a read-only grant is expressible in the protocol. Whether your MCP client lets you decline mcp:write at the consent screen is a client decision, and Whimsical's own documentation does not describe a read-only connection mode.
It returns Whimsical's own syntax and formatting guides. Whimsical documents how_to as a lookup for topics such as flowcharts, wireframes, mind maps, sequence diagrams, sticky notes, tables and boards, plus references for icons, colors and font sizes. Assistants normally call it unprompted before generating complex content, so you rarely invoke it yourself.
help.whimsical.com/integrations/remote-mcp redirects here) · retrieved 2026-08-19initialize probe returning 401 with WWW-Authenticate — 2026-08-19 · retrieved 2026-08-19Connect Whimsical once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.