Skip to main content
Glama
Sign In
draft1-mcp

draft1-mcp

by abdelhadi-azouni
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

draft1-mcp

MCP server for draft1.ai — generate and iterate on draw.io-style architecture diagrams from natural language or code (Terraform, docker-compose, Kubernetes, SQL, Mermaid, PlantUML) directly from Claude Code, Claude Desktop, Cursor, or any MCP client.

Tools

Tool

Arguments

What it does

generate_diagram

prompt (string, required), format (optional: auto | terraform | docker-compose | kubernetes | sql | mermaid | plantuml, default auto)

Creates a diagram from a description or pasted source code. Returns the share URL, a diagram_id for follow-up edits, and an XML summary.

edit_diagram

diagram_id (string, required), instruction (string, required)

Applies a plain-English change to an existing diagram (e.g. "add a redis cache between the api and the db").

Related MCP server: AI Charts

Requirements

  • Node.js >= 18.17

  • A draft1 API key — create one at app.draft1.ai (account settings)

Configuration

Environment variable

Required

Description

DRAFT1_API_KEY

yes

Your draft1 API key

DRAFT1_API_URL

no

API base URL override (default https://api.app.draft1.ai)

Install

Claude Code

# once the package is published to npm:
claude mcp add draft1 --env DRAFT1_API_KEY=YOUR_KEY -- npx -y github:abdelhadi-azouni/draft1-mcp

# from a local checkout (this repo):
npm install && npm run build
claude mcp add draft1 --env DRAFT1_API_KEY=YOUR_KEY -- node /absolute/path/to/draft1-mcp/dist/index.js

Then in Claude Code: "generate a diagram of my terraform in ./infra".

Claude Desktop

Add to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json, Windows: %APPDATA%\Claude\claude_desktop_config.json):

{
  "mcpServers": {
    "draft1": {
      "command": "npx",
      "args": ["-y", "draft1-mcp"],
      "env": { "DRAFT1_API_KEY": "YOUR_KEY" }
    }
  }
}

(For a local checkout, use "command": "node", "args": ["/absolute/path/to/draft1-mcp/dist/index.js"] instead.)

Alternatively, bundle it as a one-click Claude Desktop extension: npx @anthropic-ai/mcpb pack in this directory (uses manifest.json; prompts the user for the API key on install).

Cursor

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json in your project:

{
  "mcpServers": {
    "draft1": {
      "command": "npx",
      "args": ["-y", "draft1-mcp"],
      "env": { "DRAFT1_API_KEY": "YOUR_KEY" }
    }
  }
}

Errors

  • 401 — invalid DRAFT1_API_KEY; create/rotate a key at app.draft1.ai (account settings).

  • 402 — out of credits; top up at app.draft1.ai. Both are returned as tool errors with the server's message, so the calling agent can relay them.

Development

npm install    # also builds via the prepare script
npm test       # builds, then runs node --test against dist/ with a mocked fetch
npm start      # run the stdio server locally (requires DRAFT1_API_KEY)

The server speaks MCP over stdio; stdout is reserved for the protocol and all logging goes to stderr.

Available Tools

2 tools
edit_diagramEdit an existing diagramA

Apply a plain-English change to a diagram previously created with generate_diagram (e.g. 'add a redis cache between the api and the db'). Returns the updated share URL.

Inputs: diagram_id (required), instruction (required).

generate_diagramGenerate a diagramA

Generate a draw.io-style diagram with draft1.ai from a natural-language description or from source code (Terraform, docker-compose, Kubernetes, SQL, Mermaid, PlantUML). Returns a shareable URL plus a diagram_id for follow-up edits.

Inputs: prompt (required), format.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one creates diagrams, the other edits them. There is no overlap in functionality, so an agent can easily select the right tool based on whether a new diagram or a modification is needed.

    Naming Consistency5/5

    Both tools follow the verb_noun pattern consistently: generate_diagram and edit_diagram. This provides a predictable and intuitive naming convention.

    Tool Count3/5

    With only two tools, the set is on the thin side. For a diagram service, one might expect additional operations like list or delete, but the narrow scope of generating and editing makes the count borderline acceptable.

    Completeness4/5

    The core lifecycle of diagram creation and modification is covered. However, there is no way to list, delete, or retrieve a specific diagram by ID, which could be considered minor gaps, but the shareable URL and edit-by-ID cover the essential workflows.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers