# erd-editor [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/dineug/erd-editor  
**GitHub Stars:** 1728  
**npm Downloads (last month):** 800  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/erd-editor

## Description
Design database schemas as ERDs in your browser, VS Code, JetBrains IDEs or Obsidian. Import SQL, DBML and GraphQL, export DDL and code, and let coding agents edit live over MCP.

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

```json
"mcpServers": {
  "erd-editor": {
    "command": "npx",
    "args": ["-y","@dineug/erd-editor-mcp"]
  }
}
```

## Documentation

## What erd-editor MCP server does

The erd-editor MCP server connects coding agents to ERD Editor diagrams. It exposes one MCP tool for each editing operation, allowing an agent to make structured changes to a database schema rather than only writing text into a file.

The server works with ERD Editor's `.erd.json` document format and can operate in two modes. When a supported editor has the diagram open and its connection is enabled, the agent joins that diagram as another collaborator. When no editor is connected, the server works directly with the diagram file in the project folder.

This is a fit for workflows where a developer wants an agent to change tables, columns, relationships, or other ERD content while inspecting the result on a canvas.

## How it works

An MCP client starts the server over standard input and output. The agent then receives the available editing operations as MCP tools. In a connected VS Code, Obsidian, or JetBrains environment, the server participates in the editor's collaboration channel, so edits are reflected in the open diagram. The connected editor keeps the agent's changes in the same editing workflow, and its undo behavior can revert the agent's own changes.

With no editor attached, the server edits the `.erd.json` file on disk. An editor that has disabled its connection, or a workspace or project that is not trusted, permits reading but rejects changes. This provides a read-only path for agent access in those situations.

## Setup and configuration

Node.js 22.12 or newer is required. Install the server from the project directory with the package published as `@dineug/erd-editor-mcp`.

For Claude Code, register it with:

```sh
claude mcp add --transport stdio erd-editor -- npx -y @dineug/erd-editor-mcp
```

For Codex, use:

```sh
codex mcp add erd-editor -- npx -y @dineug/erd-editor-mcp
```

The same package can be configured in other MCP clients that support a standard stdio server. The diagram can be held by the VS Code extension, the Obsidian plugin, or the JetBrains plugin; otherwise, place the target `.erd.json` file in the project directory.

## Tools and capabilities

- Provides one MCP tool for each ERD editing operation.
- Lets agents edit diagrams displayed in VS Code, Obsidian, or JetBrains IDEs.
- Modifies `.erd.json` files directly when no editor is connected.
- Supports agent participation in an open diagram as a live collaborator.
- Preserves agent-specific undo behavior in a connected editor.
- Allows agents to read diagrams when editor connections or workspace trust prevent modifications.

## Limitations and notes

The server requires Node.js 22.12 or later. Editing is refused when an editor has disabled its connection or when the workspace or project is untrusted, although reading remains available. Live editing depends on an ERD Editor instance being open in a supported host; without one, the server works against the file on disk instead.

The MCP package is intended for the ERD Editor ecosystem. Its visual editing hosts include the web app, Google Drive, VS Code, JetBrains IDEs, and Obsidian, but the agent connection described here specifically uses the MCP server and the editor integrations that expose a diagram to it.

_Full upstream README: https://allmcps.com/mcp/erd-editor/readme_