Whimsical MCP connector for AI agents

Whimsical MCP tools for AI agents

CALL ANY TOOL

6 tools covering create, update, get.

whimsicalmcp_auto_layout

Re-arrange shapes on a whimsical flowchart using the auto-la

Re-arrange shapes on a whimsical flowchart using the auto-layout engine, with connectors re-routed automatically.

Parameters

Name

Type

Required

Description

board_id

string

Required

Board file ID

orientation

string

Optional

Layout direction (td=top-to-bottom, lr=left-to-right, bt=bottom-to-top, rl=right-to-left). Inferred from connector flow when omitted.

parent_id

string

Optional

Optional: scope layout to descendants of this object id (e.g. a group/container). Omit to lay out all root-level shapes on the file.

spacing

string

Optional

Spacing preset; defaults to 'default'.

whimsicalmcp_comment_edit

Create, reply to, edit, resolve, or delete comment threads o

whimsicalmcp_comment_read

Read all comment threads on a board item, including author,

whimsicalmcp_create

Create a new whimsical board, diagram, folder, or doc in the

Create a new whimsical board, diagram, folder, or doc in the specified workspace or folder.

Parameters

Name

Type

Required

Description

type

string

Required

What to create. Use 'board' for freeform/sketch layouts where you control absolute positions (ideal for recreating hand-drawn notes, whiteboards, or any visual layout). Use 'flowchart', 'mindmap', 'sequence_diagram', 'sticky_notes', or 'wireframe' for semantic diagrams that auto-layout.

board_id

string

Optional

Add to existing board. Omit to create new board. Required for wireframe.

data

string

Optional

Content payload. Board (freeform layout): {items: [{type:"text"|"shape"|"note"|"conn"|"icon"|"link", text, x, y, ...}], groups?: [...]}. Field names are snake_case: shape_type, from_id, to_id, temp_id, font_size, icon_name (NOT camelCase). For board items the `text` field accepts markdown (**bold**, *italic*, `code`, - bullet, 1. numbered, [label](url), # heading). URLs to Linear issues or GitHub issues/PRs render as inline badges; custom labels ([label](url)) aren't kept for these — use a bare URL. Keep one item per entity (one Linear issue, one card); put the formatting inside that item's text rather than splitting it across several items. Only emit conn items for arrows actually present in the source — do not invent connectors. Call how_to('board') for the full schema and examples. Mindmap: {markdown: "Root\n- Child\n - Grandchild"} (indented bullets). Flowchart/sequence_diagram: call how_to(type) for syntax. Wireframe: call how_to('wireframe') for flexbox DSL. Table: {markdown: "| A | B |\n|---|---|\n| 1 | 2 |"} or {columns: ["A","B"], rows: [["1","2"]]}.

parent_id

string

Optional

Folder or team id (base58) to create in. Find folder ids with file_tree, team ids with file_tree({filter:'teams'}), search, or list_workspaces. Defaults to the Private section.

placement

object

Optional

Position relative to a previous diagram's bbox (returned in every creation response). Use direction 'right' or 'below' to build grids. Mutually exclusive with x/y.

title

string

Optional

Title or name for the created item

whimsicalmcp_delete

Move a whimsical file, folder, or doc to trash, restoring it

whimsicalmcp_doc_create

Create a new whimsical document with optional markdown conte

whimsicalmcp_edit

Edit a whimsical board or doc by applying an array of add, u

whimsicalmcp_fetch

Fetch the content of a whimsical board, doc, or folder by id

whimsicalmcp_file_tree

Browse the workspace file hierarchy to list folders, boards,

whimsicalmcp_generate_diagram

Generate a whimsical flowchart, mind map, or sequence diagra

whimsicalmcp_generate_mind_map

Generate a whimsical mind map from indented markdown, where

whimsicalmcp_generate_wireframe

Generate a whimsical wireframe with flexbox layout using con

Build your Agent

Same auth pattern across every framework.

from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="whimsicalmcp")

mcp = MultiServerMCPClient({
    "whimsicalmcp": {
        "url": "https://mcp.scalekit.com/whimsicalmcp",
        "headers": {"Authorization": "Bearer " + token}
    }
})
tools = await mcp.get_tools()

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "whimsicalmcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/whimsicalmcp
// Pass: Authorization: Bearer + token

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "whimsicalmcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/whimsicalmcp
// Pass: Authorization: Bearer + token

from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="whimsicalmcp")
# Connect to MCP at https://mcp.scalekit.com/whimsicalmcp
# Pass: Authorization: Bearer + token

Try these prompts

Paste any prompt into your agent to get started.

Get started

Copy the prompt

Copied

Reflow or edit Whimsical wireframe elements using operations or a flexbox layout tree?

Copy the prompt

Copied

Search workspace files and content by name or full-text query?

Advanced

Copy the prompt

Copied

List all workspaces the authenticated user belongs to, including team IDs and member roles?

Copy the prompt

Copied

Look up Whimsical-specific syntax, examples, and guides for creating diagrams and wireframes?

SEE HOW AUTH WORKS

User authorises once. Every agent call after uses their token with scope enforcement.

Authorize

Your user connects

Whimsical MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Whimsical MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Whimsical MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Whimsical MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

No items found.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Other connector libraries treat auth as a demo afterthought.

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.

// shared token
 audit → bot_service_account

 // scalekit
 audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

One connector today. Ten tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Whimsical as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Whimsical OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Whimsical?
Yes. Pass a tool name filter to listScopedTools so the design agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Whimsical.

What happens when a user revokes Whimsical access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Which boards can the agent create or edit diagrams on?
Only boards in workspaces the authorizing user belongs to. Flowchart edits, comments, and auto-layout calls inherit the user's Whimsical role. Private boards stay untouched.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit