ER diagrams from SQL, Prisma or ORM models. One tool, no account, nothing stored.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Open an interactive ER diagram of a database schema on erddocs.com. Use it when the user wants to see, understand, review or document their database structure, or asks for an ER diagram. Pass the schema text exactly as it is in the project. It reads SQL dumps and DDL (PostgreSQL, MySQL, SQL Server, SQLite), Prisma schema.prisma, DBML, Mermaid erDiagram, PlantUML, Django models.py, SQLAlchemy models, Sequelize models, TypeORM entities and a folder of Laravel migrations (concatenate the files). For SQL, the structure is enough: no INSERT data. Returns a link. The user opens it in a browser and gets the diagram with every table and relation laid out, relations without declared foreign keys found by column name and drawn dashed, and a data dictionary. Nothing is stored on the server: the schema travels inside the link and is parsed in the user's browser. A link holds a schema of a few dozen tables (about 100–200 characters of link per table, depending on comments); for a larger one the tool says so and the user pastes it on erddocs.com instead.
The schema text as it is: SQL DDL, schema.prisma, models.py, migrations, DBML, Mermaid or PlantUML.
Only if automatic detection would get it wrong.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http erd-diagram https://erddocs.com/mcp
Open an interactive ER diagram of a database schema on erddocs.com. Use it when the user wants to see, understand, review or document their database structure, or asks for an ER diagram. Pass the schema text exactly as it is in the project. It reads SQL dumps and DDL (PostgreSQL, MySQL, SQL Server, SQLite), Prisma schema.prisma, DBML, Mermaid erDiagram, PlantUML, Django models.py, SQLAlchemy models, Sequelize models, TypeORM entities and a folder of Laravel migrations (concatenate the files). For SQL, the structure is enough: no INSERT data. Returns a link. The user opens it in a browser and gets the diagram with every table and relation laid out, relations without declared foreign keys found by column name and drawn dashed, and a data dictionary. Nothing is stored on the server: the schema travels inside the link and is parsed in the user's browser. A link holds a schema of a few dozen tables (about 100–200 characters of link per table, depending on comments); for a larger one the tool says so and the user pastes it on erddocs.com instead.
| Argument | Type | Description |
|---|---|---|
| format | string | Only if automatic detection would get it wrong. |
| schema* | string | The schema text as it is: SQL DDL, schema.prisma, models.py, migrations, DBML, Mermaid or PlantUML. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"schema"
],
"properties": {
"format": {
"enum": [
"sql",
"prisma",
"dbml",
"mermaid",
"plantuml",
"django",
"sqlalchemy",
"sequelize",
"typeorm",
"laravel"
],
"type": "string",
"description": "Only if automatic detection would get it wrong."
},
"schema": {
"type": "string",
"maxLength": 2000000,
"minLength": 1,
"description": "The schema text as it is: SQL DDL, schema.prisma, models.py, migrations, DBML, Mermaid or PlantUML."
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 5, 2026.