# LetDraw [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/letdraw/letdraw-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/letdraw

## Description
Create, edit, share and export hand-drawn LetDraw diagrams, from code or a prompt.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "letdraw": {
    "command": "npx",
    "args": ["-y","@letdraw/mcp"],
    "env": {
      "LETDRAW_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `LETDRAW_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What LetDraw MCP server does

LetDraw MCP server exposes LetDraw’s online hand-drawn whiteboard and diagramming features to MCP clients and HTTP-based scripts. The repository provides a client-side bridge, a typed REST SDK, API specifications, setup documentation, and examples; it does not contain the LetDraw application or hosted backend.

An agent can inspect available workspaces, folders, diagrams, and icons, then create, update, delete, or share diagrams according to the permissions granted to its token. Diagrams can be authored directly or generated from supported source formats and prompts. The integration also supports exporting diagrams as Mermaid or D2 and producing read-only links for sharing.

## How it works

The hosted MCP endpoint is available at `https://api.letdraw.com/mcp`, and the REST API uses `https://api.letdraw.com/api-v1`. Both accept a personal LetDraw API token in the `Authorization: Bearer` header. Tokens are created in the LetDraw app under Account → Developer.

For clients that support Streamable HTTP, connect directly to the hosted MCP endpoint. A stdio-compatible client can run the `@letdraw/mcp` package with `npx -y @letdraw/mcp`; the bridge forwards requests to the hosted service. The repository also includes `@letdraw/sdk`, a typed client for REST-based scripts.

## Setup and configuration

The stdio configuration requires Node.js 18 or newer and passes the token through the `LETDRAW_TOKEN` environment variable:

```json
{
  "mcpServers": {
    "letdraw": {
      "command": "npx",
      "args": ["-y", "@letdraw/mcp"],
      "env": { "LETDRAW_TOKEN": "ld_live_YOUR_TOKEN" }
    }
  }
}
```

For REST usage, send the same token as a bearer credential or initialize the SDK with it in application code. The repository’s client documentation covers desktop applications, Cursor, VS Code, Codex, and HTTP clients.

## Tools and capabilities

The LetDraw MCP server organizes access around token scopes:

- `diagrams:read` covers workspaces, folders, diagrams, and icons.
- `diagrams:write` covers diagram creation, updates, deletion, sharing, and from-code generation.
- `export` covers Mermaid and D2 exports.
- `ai:generate` covers diagram generation from a prompt using the caller’s own AI key.

Supported from-code examples include Compose, Kubernetes, DOT, Terraform, and SQL. Product icons can be stamped into diagrams when available through the service.

## Limitations and notes

The repository is an integration layer rather than a self-hosted LetDraw server. The LetDraw app and backend are not included. Access depends on a valid personal API token and the scopes assigned to it; operations outside those scopes will not be available. Prompt-based generation uses the user’s own AI key, and the integration’s hosted endpoints and token requirements must be used for the supplied bridge and SDK examples.

_Full upstream README: https://allmcps.com/mcp/letdraw/readme_