Whimsical MCP connector
The Whimsical connector brings flowcharts, wireframes, mind maps, docs and comments into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so your team can find, create and edit boards in plain language while every change is logged.
- Connects over OAuth
- Free 14-day trial
- No credit card
Turn the onboarding spec into a flowchart in the Product workspace
Working in Whimsical with Elaichi
-
Search
-
List workspaces
-
Fetch
How to connect Whimsical to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Whimsical MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Whimsical MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Whimsical MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Whimsical MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Whimsical to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Whimsical through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Whimsical is logged.
-
Product
Turn a written spec into a flowchart
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.
-
Design
Sketch a first wireframe from a brief
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.
-
Engineering
Diagram the system before the review
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.
-
Marketing
Map a campaign as a mind map
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.
-
Operations
Keep the workspace tree in order
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.
-
Research
Work through comments on a board
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.
Try asking
- “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”
What connecting Whimsical gets you
6 screens from Elaichi, each doing one job for your Whimsical account.
Ask Elaichi to work across your apps.
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
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about any Whimsical board in plain language.
The agent reads live boards, diagrams and comments and answers from what is actually there.
Copy the endpoint
AI apps
One endpoint puts Whimsical in every client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, with no SDK and no shared API key.
Tool catalog
17 Whimsical tools, ready without writing code.
Search, create, edit, move and comment on boards, diagrams, wireframes and docs.
Toolboxes
Every team gets its own Whimsical toolbox.
Design, Product and Engineering each work from a toolbox scoped to their boards.
Shared connections
Teammates work in Whimsical without seeing a credential.
One person connects Whimsical, shares it with teams, and the log still names each person.
Audit log
Every Whimsical change has a name beside it.
When, who, what happened and which board, kept in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Whimsical digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch boards
Whimsical
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Whimsical
Queued
Workflows
A schedule drafts the Whimsical digest itself.
New boards are fetched, grouped and summarized, a person approves, and it posts back to Whimsical.
Whimsical health
Refreshed 4 minutes ago · every 15 minutes · from the boards collection
Boards
1,284 ↓ 12%
Diagrams
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Boards created
Last 14 days
By team
Share of activity
Product 34%
Design 27%
Engineering 21%
Marketing 18%
Collections and dashboards
Whimsical health, counted without asking a model.
Four metrics, fourteen days of boards created and a team breakdown, refreshed on a schedule.
Why connect Whimsical's MCP server through Elaichi
Whimsical builds and runs this MCP server. Elaichi sits in front of it, so Whimsical's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Whimsical's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach Whimsical's tools at the same Elaichi address as every other connected app. Nobody adds Whimsical's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own Whimsical sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Whimsical's server. By default, a tool Whimsical does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to Whimsical
Whimsical builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Whimsical team.
For IT and engineering
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.
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 | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Whimsical tools for your AI agents
17 tools are ready to call through Elaichi's MCP endpoint the moment you connect Whimsical, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Whimsical builds and runs these tools.
No tools match your search.
Questions, answered
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, Microsoft Copilot, 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 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 restricting delete, move or edit. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot 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, Microsoft Copilot, 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.
Put Whimsical in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot