AI Diagram Maker

io.github.erajasekarPublished by GitHub account erajasekarv1.0.0Updated Oct 24, 2026

Generate software diagrams from natural language, code, ASCII, images, Mermaid.

The publisher's own server: Diagram

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

AI-generated overview

Turns natural language, JSON, ASCII, images or Mermaid into software diagrams (flowchart, sequence, ERD, architecture, UML) via the AI Diagram Maker service.

What you can do
  • Generate diagrams from a plain-English description, with an optional diagram type and styling prompt
  • Convert JSON structures such as API responses, schemas or config files into a diagram
  • Turn ASCII art or a whiteboard photo, screenshot or image URL into a clean diagram
  • Convert Mermaid source into D2 and return a PNG image
  • Return a diagram URL and render diagrams inline in the chat
When to use it
Useful when you want an assistant to sketch architecture, sequence, ERD or UML diagrams while you work in Cursor, Claude Desktop, Claude Code or another MCP client, including turning existing Mermaid, JSON or whiteboard images into polished diagrams.
Requirements
Either the hosted HTTP endpoint (no install) or the local npm package run with npx, which needs Node.js 18+. An AI Diagram Maker account and API key are required: sent as the X-ADM-API-Key or Authorization Bearer header for HTTP, or as the ADM_API_KEY environment variable for stdio. Network access to the service is needed.
Before you install
The API key is a secret; keep it out of shared configs and logs. Diagram content, including image URLs or base64 images and code or JSON you submit, is sent to the third-party AI Diagram Maker service. Debug logging (ADM_DEBUG) writes request parameters and API payloads to stderr. Diagrams are created on your account, which may consume service quota or credits.

Installation

In SourceWeft

  1. Open AI Diagram Maker in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

AI Diagram Maker MCP Server

MCP server for AI Diagram Maker — generate beautiful software engineering diagrams directly inside Cursor, Claude Desktop, Claude Code, or any MCP-compatible AI agent.

Features

  • 5 tools covering every input type: natural language text, code, ASCII diagram, images, and Mermaid
  • Inline rendering — diagrams appear directly in the chat using MCP Apps UI, no downloads
  • Diagram URL in responses — open it in your browser to view and edit the diagram
  • 5 diagram types: flowchart, sequence, ERD, system architecture, UML
  • Supports both stdio (local) and HTTP/Streamable HTTP (remote) transports

Contents

Prerequisites

  1. Node.js 18+
  2. An AI Diagram Maker account and API key

Hosted MCP server

The public MCP endpoint is https://mcp.aidiagrammaker.com/mcp (Streamable HTTP). Nothing to install for this option.

Authentication (HTTP)

For remote HTTP clients, send your API key on every request — not via environment variables:

  • X-ADM-API-Key: <your_api_key> (recommended), or
  • Authorization: Bearer <your_api_key>

Use the API key from your AI Diagram Maker account (see Prerequisites).

Remote server JSON example

Merge this into your client’s MCP config (replace the API key placeholder):

json
{  "mcpServers": {    "ai-diagram-maker": {      "url": "https://mcp.aidiagrammaker.com/mcp",      "headers": {        "X-ADM-API-Key": "YOUR_API_KEY"      }    }  }}

Installation

Option A — hosted server (recommended)

Use the remote server JSON example above and wire it into your client using MCP client configuration. No global install.

Option B — run locally with npx

Nothing to install permanently — npx runs the package on demand. The package name is ai-diagram-maker-mcp; append @latest if you want every invocation to resolve the newest release (recommended for one-off runs and claude mcp add).

bash
ADM_API_KEY=your_api_key npx ai-diagram-maker-mcp@latest

MCP client configuration

Cursor

Remote (recommended)

Add to ~/.cursor/mcp.json or Settings → MCP using the remote server JSON example. No environment variables are required for this setup.

Local (stdio)
json
{  "mcpServers": {    "ai-diagram-maker": {      "command": "npx",      "args": ["-y", "ai-diagram-maker-mcp@latest"],      "env": {        "ADM_API_KEY": "your_api_key_here"      }    }  }}

Optional: add "ADM_DEBUG": "1" to env for debug logging — see Environment variables.

Claude Desktop

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

json
{  "mcpServers": {    "ai-diagram-maker": {      "command": "npx",      "args": ["-y", "ai-diagram-maker-mcp@latest"],      "env": {        "ADM_API_KEY": "your_api_key_here"      }    }  }}

Claude Code

macOS
bash
claude mcp add ai-diagram-maker -t stdio -e ADM_API_KEY=<api_key> -- npx -y ai-diagram-maker-mcp@latest
Windows
bash
claude mcp add ai-diagram-maker \  --command "npx" \  --args "-y,ai-diagram-maker-mcp@latest" \  --env ADM_API_KEY=your_api_key_here

HTTP transport (local or self-hosted)

To run an HTTP server yourself (same header-based auth as Authentication (HTTP)):

bash
npx ai-diagram-maker-mcp@latest --transport http

The server listens on $PORT or 3001. Point clients at /mcp and send the API key with each request using the headers above.

Environment variables

VariableRequiredDefaultDescription
ADM_API_KEYYes (stdio only)—Your AI Diagram Maker API key (stdio transport only; remote HTTP clients use headers — see Authentication (HTTP))
ADM_BASE_URLNohttps://app.aidiagrammaker.comOverride for local/staging API; also used as the base for diagram URLs in tool responses
ADM_DEBUGNo—Set to 1, true, or yes to log request parameters from the AI agent and the payload sent to the AI Diagram Maker API. Logs go to stderr. In Cursor, open Output, choose the MCP or ai-diagram-maker channel to read the server logs.

Tools

generate_diagram_from_text

Generate a diagram from a natural language description.

ParameterTypeRequiredDescription
contentstringYesNatural language description of the diagram
diagramTypeenumNoflowchart, sequence, erd, system_architecture, uml
promptstringNoAdditional styling/layout instruction

Example prompts:

  • "Create a microservices architecture with API gateway, auth service, user service, and PostgreSQL database"
  • "Draw a sequence diagram for user login flow with JWT token generation"
  • "adm show the CI/CD pipeline for a Next.js app deployed to Vercel"

generate_diagram_from_json

Convert a JSON structure into a diagram (great for API responses, database schemas, config files).

ParameterTypeRequiredDescription
contentstringYesJSON string to visualise
promptstringNoHow to interpret the JSON
diagramTypeenumNoPreferred diagram type

generate_diagram_from_ascii

Convert ASCII art into a polished diagram.

ParameterTypeRequiredDescription
contentstringYesRaw ASCII art diagram
promptstringNoRendering instructions
diagramTypeenumNoPreferred diagram type

generate_diagram_from_image

Convert a whiteboard photo, screenshot, or any image into a clean diagram.

ParameterTypeRequiredDescription
contentstringYesPublic image URL or base64 data URI
promptstringNoWhat to extract or how to render
diagramTypeenumNoPreferred output diagram type

generate_diagram_from_mermaid

Convert a Mermaid diagram definition to D2 and return a PNG image.

ParameterTypeRequiredDescription
contentstringYesMermaid diagram source (e.g. flowchart, sequenceDiagram, erDiagram)
promptstringNoOptional layout or styling instruction
diagramTypeenumNoPreferred diagram type for the converted output

Trigger keywords

The AI agent will automatically select the right tool when you use phrases like:

  • adm ...
  • ai diagram maker ...
  • create a diagram of ...
  • show me a flowchart / sequence diagram / ERD / architecture ...
  • visualise / draw / diagram ...

Local developer setup

Use these steps to clone the repo, build locally, and run the MCP server with Node.

1. Clone the repository

bash
git clone https://github.com/erajasekar/ai-diagram-maker-mcp.gitcd ai-diagram-maker-mcp

2. Install dependencies

bash
npm install

3. (Optional) Regenerate API client

If you change the AI Diagram Maker OpenAPI spec or config, regenerate the client:

bash
npm run generate

4. Build

bash
npm run build

This compiles TypeScript and builds the MCP app UI into dist/. The server entrypoint is dist/index.js.

5. Run the local MCP server

stdio (default) — for use with Cursor, Claude Desktop, etc.:

bash
ADM_API_KEY=your_api_key node dist/index.js

Or use the npm script:

bash
ADM_API_KEY=your_api_key npm start

HTTP transport — for remote clients or testing (same headers as Authentication (HTTP)):

bash
ADM_API_KEY=your_api_key node dist/index.js --transport http

Or:

bash
ADM_API_KEY=your_api_key npm run start:http

The HTTP server listens on $PORT (default 3001).

6. Use the local server in Cursor

Point Cursor at your built server via Settings → MCP (or ~/.cursor/mcp.json):

json
{  "mcpServers": {    "ai-diagram-maker": {      "command": "node",      "args": ["/absolute/path/to/ai-diagram-maker-mcp/dist/index.js"],      "env": {        "ADM_API_KEY": "your_api_key_here"      }    }  }}

Replace /absolute/path/to/ai-diagram-maker-mcp with the actual path to your cloned repo. After changing the config, restart Cursor or reload the MCP servers.

For debug logging, add "ADM_DEBUG": "1" to env — see Environment variables.

License

MIT

Source: README.md at commit f24e513

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Diagram integrations