Sketchdex MCP server

Read from the package source without running it. The installed server may list more.

• add_elements

  Append elements to a scene, leaving everything already there untouched. The usual way to draw something new.

• check_scene

  Find layout problems by geometry instead of by looking: text hidden behind a filled shape drawn after it, captions running past the panel they sit in, labels too tall for their container, zero-size elements, broken arrow bindings, strays parked far off, exact duplicates. Each finding carries the element ids, so the fix is one update_elements call. Run it after a batch of drawing - it is far cheape

• create_scenewrite action

  Make a new scene, optionally with its starting elements.

• delete_elementswrite action

  Remove elements by id.

• describe_scene

  What is on a scene, as structure rather than pixels: counts by type, overall bounds, and a rounded summary of each element with its id, position, size, text and bindings. Cheaper than read_scene and usually enough to plan an edit.

• list_history

  Snapshots held for a scene, newest first.

• list_scenes

  Every scene in the vault with its id, name, element count and last-edited time. Start here.

• move_elements

  Shift a set of elements by dx, dy in one write, keeping everything else about them. Select by ids, groupIds (an import_svg piece), a region box, or any mix. A container's label always moves with it, and an arrow bound to something that moves keeps that end attached (include the arrow itself to move it whole). Returns the new bounds of what moved.

• read_elements

  Full, unabridged elements, filtered down to the ones you need. Use this rather than read_scene when editing a few things in a busy scene.

• read_scene

  The whole scene exactly as stored, plus the path to the .excalidraw file on disk. Large scenes run to thousands of elements, so prefer describe_scene or read_elements unless you genuinely need everything. The path is there for edits no tool here covers - take a snapshot first if you use it.

• render_scene

  A PNG of the scene as it actually renders, so you can look at what you drew. Use it to check your own work - proportions, overlaps, whether the thing reads as the thing. Always written to a file as well as returned. A tall or wide page (long edge more than about twice the short one, and too big to fit at the asked size) comes back as a few tiles cut along its length, each with the scene box it sho

• replace_scene

  Replace a scene's entire contents. Destructive by design - the previous state is snapshotted, but prefer add_elements or update_elements when you only mean to change part of it.

• restore_snapshotwrite action

  Put a snapshot back on the canvas. This is itself snapshotted, so reverting a revert is possible.

• set_background

  Set the paper: the scene's real background colour, shown exactly as given (never inverted). The default pen for hand drawing follows it, so the next stroke in the app is visible. Elements already drawn keep their colours - recolour their ink yourself if you flip a scene from light to dark or back. New scenes start on dark paper (#121212).

• sketchdex_docs

  The manual, for answering the user's questions and fixing problems without guessing: install on any client, where scenes are stored and how to move the vault, the library app, what rendering needs, every tool, the drawing contract, and troubleshooting for the errors that come up. No topic returns the index.

• sketchdex_info

  Version of this server, where it is running from, which vault it is using, and how long this process has been alive. Use it to confirm you are talking to the build you think you are.

• snapshot_scene

  Stash the current state without changing anything, so it can be restored from the history sidebar. Do this before editing a .excalidraw file directly with your own file tools - every other tool here snapshots on its own.

• update_elementswrite action

  Change named fields on existing elements. Send only what changes - {id, x: 40} moves one box and leaves its other 25 fields alone. Pass a list in `elements`, each carrying its `id`, or use `ids` + `patch` to apply one change across many.

• Code scan193 source files scanned20/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 42 days ago12/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

80/100

higher than 60% of 48,243 servers

Tools

18

the typical server has 7

Tools that change things

22%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

1

more than 65% of 28,706 servers

Downloads a week

40

more than 30% of 12,306 servers with a package

Grade history

• 2026-10-16downgradeA → Bscore 80: Google API key in source (often public by design; check its restrictions)

Sketchdex: common questions

Is Sketchdex MCP server safe?

Mostly: it is graded B (80/100). Read the Sketchdex safety report

How do I install Sketchdex?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Sketchdex need an API key?

No secret keys are declared. It reads 2 settings from the environment.

Is Sketchdex maintained?

The last commit was 62 days ago (2026-09-04). The latest release is v0.1.2.

What can I use instead of Sketchdex?

Servers from other publishers that do the same job: draw.io MCP server.

How does Sketchdex compare with other MCP servers?

safety score 80/100 (higher than 60% of 48,243 servers); tools 18 (the typical server has 7); tools that change things 22% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.