# Whimsical MCP connector

The Whimsical connector brings flowcharts, wireframes, mind maps, docs and comments into Claude, ChatGPT, Cursor and the Elaichi Agent, so your team can find, create and edit boards in plain language while every change is logged.

Source: https://elaichi.ai/connectors/whimsical/

## Facts

| | |
| --- | --- |
| Application | Whimsical |
| Category | Design |
| AI tools | 17 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Whimsical builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | whimsical.com/contact |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Whimsical is connected

- Turn the onboarding spec into a flowchart in the Product workspace
- Draft a wireframe for the new settings page
- Summarize the open comments on the checkout redesign board

## Connect Whimsical in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Whimsical.
2. Optionally set Share with, then press Connect.
3. Approve it in Whimsical. Whimsical's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Whimsical tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Whimsical MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Whimsical MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## Whimsical MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Whimsical to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Whimsical tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Whimsical through Elaichi

### Turn a written spec into a flowchart

Product. Paste the spec or point at the doc, and the agent drafts the user flow as a Whimsical flowchart in the right workspace. Review it, ask for a branch to be added, and it edits the board in place.

### Sketch a first wireframe from a brief

Design. Describe the screen and the agent generates a wireframe you can open and refine in Whimsical. Ask for a second version with the navigation moved and it updates the same board.

### Diagram the system before the review

Engineering. Hand over the service names and how they talk to each other, and the agent draws the architecture diagram and tidies the layout. Change a dependency later and ask it to redraw the affected part.

### Map a campaign as a mind map

Marketing. Start from a theme and a launch date, and the agent builds a Whimsical mind map of channels, messages and owners. Add a branch for each new idea as the planning call goes on.

### Keep the workspace tree in order

Operations. Ask what lives in a folder, move stale boards to an archive folder, or delete the duplicates left over from a workshop. The agent walks the file tree so you do not have to click through it.

### Work through comments on a board

Research. Ask for every open comment on the journey map and get them summarized by theme. Reply to the ones you can resolve and leave the rest for the author, all without leaving the chat.

## Elaichi vs Zapier MCP vs Composio for Whimsical

All three can connect Whimsical to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Whimsical tools | Allow or restrict single Whimsical tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Whimsical call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Whimsical to Claude?

Connect Whimsical in Elaichi first, which opens Whimsical's own sign-in window where you approve access over OAuth, with no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks and Whimsical is ready to use.

### Does Whimsical work with ChatGPT and Cursor as well as Claude?

Yes. Once Whimsical is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, the Elaichi Agent and any other MCP client. You connect Whimsical once and every client sees it.

### What can an AI agent actually do with my Whimsical data?

An agent can search your Whimsical workspaces, open a board or doc, and generate flowcharts, mind maps and wireframes from a plain description. It can edit an existing board, tidy the layout, move or delete files, and read and reply to comments. Short, concrete asks such as "add a login step to the checkout flow" work better than long paragraphs.

### Does connecting Whimsical give the AI access to every workspace?

No. Every call to Whimsical runs as the person who signed in, so the agent only sees the workspaces, boards and docs that person can already open in Whimsical. Elaichi can narrow that further with restrictions, but it can never grant more than Whimsical itself allows.

### Can my team share one Whimsical connection?

Yes. One person connects Whimsical in Elaichi and shares it with a team, and nobody else ever handles a credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every board created or comment edited in Whimsical.

### Can I stop an agent from deleting or changing things in Whimsical?

Yes. Restrictions in Elaichi apply per action, so you can allow searching and creating in Whimsical while blocking delete, move or edit. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it.

### What happens to a Whimsical connection when someone leaves?

Offboarding that person in Elaichi ends their access to Whimsical through every client at once. A Whimsical connection they shared keeps working for everyone else on the team. If you want it gone entirely, disconnect Whimsical once in Elaichi and it disappears from Claude, ChatGPT, Cursor and the Elaichi Agent together.

### Does the Whimsical MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Whimsical is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Whimsical?

Yes. Both let Claude, ChatGPT or Cursor use Whimsical. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Whimsical call.

### How is Elaichi different from Composio for Whimsical?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Whimsical: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 17 Whimsical tools

Every tool below is callable through https://api.elaichi.ai/mcp once Whimsical is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Search** (Search). Search across your Whimsical workspace by title or content. Use this to find existing boards, docs, folders, and sections before creating something new, or to pull relevant files into context. Supports filtering to file and folder titles only, or searching across all content,…
- **Fetch** (Action). Read the contents of a Whimsical board, doc, or folder by ID. Returns the text content of the file. For boards, this includes all shapes, sticky notes, text, and diagram nodes. For docs, it returns the full text. Can also return a PNG image snapshot of a board. Use search…
- **File tree** (Action). Browse the folder hierarchy in your workspace. Use this to see how files are organized, find a specific folder to create new content in, or get an overview of a project area.
- **List workspaces** (List). List all Whimsical workspaces you belong to. Returns workspace names, IDs, and your role (member or guest). Useful when you have access to multiple workspaces and need to target the right one.
- **How to** (Action). Look up Whimsical-specific syntax and formatting guides before creating content. Returns guides for topics like flowcharts, wireframes, mind maps, sequence diagrams, sticky notes, tables, and boards, as well as reference lookups for icons, colors, and font sizes. AI assistants…
- **Create** (Create). Create a new Whimsical file: a board, flowchart, mind map, sequence diagram, wireframe, sticky note set, or table. This is the primary tool for generating new visual content. Diagrams are auto-laid-out; boards support freeform placement. New files are created in your…
- **Generate diagram** (Generate). Create an auto-laid-out flowchart, mind map, or sequence diagram in a single step. A convenience wrapper around create for semantic diagrams. It makes the file and lays it out automatically, so it's a good fit when the structure matters more than exact positioning. For…
- **Generate mind map** (Generate). Create a mind map from an indented outline. Give it a simple outline (a root topic with nested children) and it builds and lays out the mind map automatically. Mind maps are horizontal by default (branches to the left and right); ask for a vertical layout to get a top-down tree.
- **Generate wireframe** (Generate). Create a UI wireframe with an automatic flexbox layout. Builds a wireframe from a description of the screen (containers, buttons, inputs, images, and icons) and arranges everything with flexbox so it stays aligned.
- **Doc create** (Create). Create a new Whimsical document with markdown content. Supports headings, lists, links, code blocks, and tables. Use this for text-heavy content rather than create .
- **Edit** (Action). Add, update, or delete objects on an existing Whimsical board or doc. For boards: add shapes, text, sticky notes, connectors, icons, and tables; update position, color, size, or text; delete objects. Colors can be palette keywords or custom hex values, and connector labels can…
- **Wireframe edit** (Action). Reflow or edit the elements of an existing wireframe. Add, restyle, or rearrange wireframe elements (buttons, inputs, text, and containers), then re-run the flexbox layout so everything stays aligned. Use this to iterate on a wireframe created with create ; the generic edit…
- **Auto layout** (Action). Re-arrange a flowchart using automatic layout. Useful after adding or editing shapes to clean up positioning. Connectors re-route automatically. Supports top-to-bottom, left-to-right, and other orientations, as well as compact and default spacing.
- **Delete** (Delete). Delete a Whimsical file, or objects within a board. Removes a board, doc, folder, or diagram from your workspace, or deletes specific objects from a board. Deleted files are moved to the Whimsical trash, so they can be recovered.
- **Move** (Move). Move a file or folder to a different location in your workspace. Use this to reorganize content you find elsewhere, for example after search turns up boards that are empty, untitled, or long untouched. Works well paired with search: find what needs to move, then move it.
- **Comment read** (Action). Read the comment threads on a Whimsical board or doc. Returns all threads with their author, timestamp, and content. Can read all comments on a file, or filter to comments on a specific object or block. Useful for pulling design feedback or decisions into context before making…
- **Comment edit** (Action). Create, reply to, edit, resolve, reopen, or delete a comment thread on a Whimsical board or doc. In docs, comments can be attached to a specific text selection or block (inline comments) as well as to the doc itself. Useful for leaving notes, recording decisions, or flagging…