DEV Community

Cover image for Introducing Excaliclaw: A Skill for OpenClaw to Generate Excalidraw Diagrams
Nick Taylor
Nick Taylor Subscriber

Posted on

Introducing Excaliclaw: A Skill for OpenClaw to Generate Excalidraw Diagrams

OpenClaw Challenge Submission 🦞

This is a submission for the OpenClaw Writing Challenge

I already use the Excalidraw Model Context Protocol (MCP) remote server in Claude and ChatGPT, but I was curious how it would work in OpenClaw. In Claude and ChatGPT, the MCP renders the diagram inline. I can iterate, see changes in real time, edit directly, and when I am happy, open it in Excalidraw.

Excalidraw MCP app running in Claude

OpenClaw does not render the MCP's UI, so the challenge was getting my OpenClaw, McClaw to generate the scene and hand me back a shareable Excalidraw link instead. Also, meet McClaw!

My OpenClaw named McClaw

Setting it up was straightforward. I pointed McClaw at the Excalidraw MCP server repository, the readme includes a link to the remote MCP, and asked it to configure itself. The one thing I had to specify was to use streamable HTTP instead of Server Sent Events (SSE) for the MCP transport, since OpenClaw defaults MCPs to SSE (deprecated in the MCP specification in favour of streamable HTTP).

My first test was intentionally tiny: one box that said "hello world." The MCP render worked, but the first Excalidraw share link opened an empty scene. The fix: ask it to export a full native Excalidraw scene payload, not just the MCP streaming element data.

conversation with McClaw to get a simple box with text to render

Once I was more specific, it rendered correctly.

A simple diagram with a box with the text Hello World

From there, I thought everything was fixed so I went with a more complicated diagram. McClaw and I tried a Kubernetes diagram. The boxes rendered, but labels disappeared. A later version had labels, but not the hand-drawn Excalifont. After a few rounds of iteration, McClaw and I landed on a reliable pattern:

  • Use explicit text elements instead of relying on Excalidraw/MCP label shortcuts.
  • Put text on top of shapes in the draw order.
  • Set fontFamily: 1 so text uses Excalidraw's hand-drawn Excalifont.
  • Include width and height on text elements.
  • Keep diagram elements large enough to read in chat previews.
  • Route arrows around labels where possible.
  • Never return an Excalidraw link unless the exported scene has real elements in it.

You can see the progression in the links generated along the way:

That debugging process turned into a small OpenClaw skill McClaw and I built called Excaliclaw.

The skill packages everything McClaw and I worked out from the failed exports, missing labels, font weirdness, and arrow-routing issues. Now when I ask for a diagram, McClaw has a repeatable recipe instead of the two of us rediscovering those edge cases on every run.

Now arrows actually connect boxes, and labels are grouped with their shapes.

Here's an example of the skill in action for an OAuth/OIDC login flow for a web app.

OAuth/OIDC Login Flow for a Web App in Excalidraw demonstrating that a box is linked to an arrow

If you want to use it, install it via OpenClaw:

openclaw skills install excaliclaw
Enter fullscreen mode Exit fullscreen mode

or, install it from GitHub using npx skills:

npx skills add nickytonline/skills --skill excaliclaw
Enter fullscreen mode Exit fullscreen mode

MCP gives the assistant access to a specialized tool. The skill captures the practical lessons that make it reliable.

If you want to stay in touch, all my socials are on nickyt.online.

Until the next one!

Top comments (0)