Sqemo

io.github.sqemo

Design ERDs with your team's naming standards: query/edit entities and relationships, SQL/DBML

Add to Cursor Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "io.github.sqemo-sqemo": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ]9    }10  }11}

.cursor/mcp.jsonMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y [email protected]

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1claude mcp add io.github.sqemo-sqemo -- npx -y sqemo-mcp@2.8.3

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.sqemo-sqemo": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ]9    }10  }11}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 2.8.3
Last checked: 2026-10-28

Stars: —
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Sqemo?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Sqemo need an API key?

No required environment variable is listed on this record.

What transport does Sqemo use?

Sqemo runs locally over stdio.

When was Sqemo last checked?

Last checked 2026-10-28. Design ERDs with your team's naming standards: query/edit entities and relationships, SQL/DBML

From the publisher

Documentation

sqemo-mcp

MCP server for Sqemo — AI agents that follow your team's database naming standard.

Your agent models in business terms ("Customer Number"); the column comes out as cust_no because your word list says customer → cust, number → no (case and delimiter are rules too, so CUST_NO is one setting away). Same input, same name, every table, every agent. Overrides are allowed but flagged, and a CLI lint catches drift in CI.

{ "mcpServers": { "sqemo": { "command": "npx", "args": ["-y", "sqemo-mcp"] } } }

Works with Claude Code, Claude Desktop, Cursor, and any MCP client. Local .erd.json files need no account; cloud ERDs and Pro tools need npx sqemo-mcp login.

What it looks like

Model a discussion board where members post articles, a post can be a reply to another post, and members comment on posts.

The agent calls the tools with logical names and never types a column name:

upsert_entity    { logicalName: "Post" }
// → { physicalName: "POST" }

upsert_attribute { logicalName: "Post Content", domain: "Content" }
// → { physicalName: "POST_CNTS" }          // Content → CNTS: from the team word list

upsert_attribute { logicalName: "Delete Flag", domain: "Flag" }
// → { physicalName: "DELETE_YN" }          // Flag → YN: same rule in every table

lint_erd
// → naming drift, missing words, referential integrity — before any DDL is written

CNTS and YN are not the agent's taste. They are your word list's abbreviations, applied the same way they were applied in every other table your team has modelled. Domains carry the data type, so Content is varchar(1000) everywhere it appears.

Full walkthrough with every tool call: Describe the work, get a governed schema.

Overview

AI agents can query and edit entities, relationships, and domains; generate physical names from a shared team glossary; import/export SQL (7 dialects) and DBML; and compare the model against a live database. Works with both local .erd.json files and ERDs stored on the Sqemo cloud.

npm: sqemo-mcp
Official MCP Registry: io.github.sqemo/sqemo
Web app: app.sqemo.com

Requires Node.js >= 22. Local-file tools work without any account or configuration. Login is needed for cloud ERD tools, and for the tools marked (Pro) below.

Installation

Claude Code (`.mcp.json`)

{
  "mcpServers": {
    "sqemo": { "command": "npx", "args": ["-y", "sqemo-mcp"] }
  }
}

Claude Desktop

Add the same mcpServers entry to your config file:

Windows: %APPDATA%\Claude\claude_desktop_config.json
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Cursor (`.cursor/mcp.json`)

{
  "mcpServers": {
    "sqemo": { "command": "npx", "args": ["-y", "sqemo-mcp"] }
  }
}

Login (cloud ERDs and Pro tools)

npx sqemo-mcp login    # pick Google, GitHub, or email + password
npx sqemo-mcp logout   # removes stored credentials

login asks how you want to sign in. Google and GitHub open a browser tab, complete a PKCE OAuth flow, and hand the session back through a one-shot loopback server on 127.0.0.1; the third option takes an email and password in the terminal. Only a refresh token is ever stored.

Credentials are stored in ~/.erdmaker/credentials.json (mode 0600 on POSIX); your password is never persisted.
Non-interactive shortcuts: --password forces the email + password path, --provider google|github forces a browser path.
Piped input skips the menu and goes straight to email + password, so existing automation keeps working: printf 'email\npassword\n' | npx sqemo-mcp login
The browser paths need a browser on the same machine (the callback returns to 127.0.0.1). Over SSH or in CI, use --password or the SQEMO_EMAIL / SQEMO_PASSWORD environment variables.

What you can do

36 tools in total.

Read (17 tools)

Tool	Description
`list_erds` / `list_workspaces`	Cloud ERDs and workspaces you belong to (login required)
`get_erd_overview`	Name, dialect, entity/relationship/domain/glossary stats
`list_entities` / `get_entity`	Entity list and full detail (attributes, keys, logical/physical mapping)
`list_relationships`	Relationships with endpoints and cardinality
`list_domains`	Domain definitions (also from workspace standard glossaries)
`search_dictionary`	Search the team glossary (logical/physical words, abbreviations, synonyms)
`check_naming`	Check a logical name against the team naming standard
`generate_physical_name`	Logical name → physical name via glossary + naming rules
`export_sql`	CREATE TABLE SQL — mysql, postgres, cubrid, oracle, sqlserver, sqlite, h2
`export_dbml`	DBML text
`validate_erd` / `lint_erd`	Structural validation and full lint (naming drift, referential integrity, duplicates)
`diff_erds`	Diff two sources (files, cloud ERDs, or raw SQL/DBML text) — dry-run before imports
`export_alter_sql`	Migration (ALTER) script from the physical diff against a baseline — renames stay renames via stable IDs, destructive changes come commented out (Pro)
`list_proposals`	Glossary proposal queue status (login required)

Live database (2 tools)

Read-only against your own database. Both query only the information schema — never table data — and the connection URL is used by this local process only, never sent to Sqemo servers.

Tool	Description
`introspect_db`	Import a live PostgreSQL/MySQL schema into an existing ERD (Pro)
`check_db_drift`	Check a live database or a schema dump against the ERD's physical model — missing/extra tables and columns, PK/FK/NOT NULL mismatches (Pro)

Write (17 tools)

Tool	Description
`create_erd`	New ERD from scratch or from SQL/DBML text — to a file or the cloud
`upsert_entity` / `delete_entity`	Entity editing with automatic physical-name derivation
`upsert_attribute` / `delete_attribute`	Attribute editing — PK rules and FK propagation handled automatically
`upsert_relationship` / `delete_relationship`	Relationship editing with automatic FK derivation
`upsert_domain` / `delete_domain`	Domain definition editing
`upsert_dictionary_word` / `delete_dictionary_word`	Glossary editing (standard-linked glossaries are protected)
`update_naming_rules`	Naming rule editing (delimiter, case, unknown-word handling)
`import_sql` / `import_dbml`	Replace an ERD from parsed SQL/DBML (IDs preserved)
`auto_layout`	Automatic entity/table layout (dagre)
`propose_dictionary_word` / `withdraw_proposal`	Propose new glossary words for owner approval

Cloud writes require owner or shared-editor permission and are protected by version CAS with 3-way auto-merge for concurrent edits.

CLI for CI pipelines

Offline, file-based subcommands (no login needed):

# Naming-standard check — exits 1 on violations, great as a CI gate
npx sqemo-mcp lint schema.erd.json

# Schema export to stdout
npx sqemo-mcp export schema.erd.json --format sql --dialect postgres > schema.sql
npx sqemo-mcp export schema.erd.json --format dbml > schema.dbml

Drift mode compares the model against a real database or a dump, and exits 1 when they disagree (Pro, requires login):

npx sqemo-mcp lint schema.erd.json --db "$DATABASE_URL" [--db-schema public] [--strict]
npx sqemo-mcp lint schema.erd.json --schema dump.sql --dialect postgres
npx sqemo-mcp lint --erd <cloud-erd-id> --db "$DATABASE_URL" --ignore 'tmp_*'

GitHub Actions example:

- run: npx sqemo-mcp lint schema.erd.json
- run: npx sqemo-mcp lint schema.erd.json --db "${{ secrets.DATABASE_URL }}"

Environment variables

Variable	Purpose
`SQEMO_EMAIL` / `SQEMO_PASSWORD`	Non-interactive login for CI and SSH sessions (no browser needed)
`ERDMAKER_HOME`	Override the credentials directory (default `~/.erdmaker`)
`ERDMAKER_SUPABASE_URL`	Override the API URL (defaults to the Sqemo cloud)
`ERDMAKER_SUPABASE_ANON_KEY`	Override the API publishable key
`ERDMAKER_MAX_REQUESTS_PER_MINUTE`	Per-minute request cap (default `120`, `0` disables)
`ERDMAKER_MAX_REQUESTS_PER_DAY`	Daily request cap (default `10000`, `0` disables)

The request caps are a safety net against agents stuck in loops; exceeding them returns a rate_limited error that tells the agent to stop and notify the user.

Errors

All tool errors return { code, message } — e.g. not_authenticated, no_permission, save_conflict (retry after re-reading), validation_failed, rate_limited.

License

MIT

Sqemo

io.github.sqemo

Design ERDs with your team's naming standards: query/edit entities and relationships, SQL/DBML

Databases

Add to Cursor Add to VS Code Run on PlugMCP

GitHub npm Website

Add to Cursor Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "io.github.sqemo-sqemo": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ]9    }10  }11}

.cursor/mcp.jsonMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y [email protected]

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1claude mcp add io.github.sqemo-sqemo -- npx -y sqemo-mcp@2.8.3

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.sqemo-sqemo": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ]9    }10  }11}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 2.8.3
Last checked: 2026-10-28

Stars: —
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Sqemo?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Sqemo need an API key?

No required environment variable is listed on this record.

What transport does Sqemo use?

Sqemo runs locally over stdio.

When was Sqemo last checked?

Last checked 2026-10-28. Design ERDs with your team's naming standards: query/edit entities and relationships, SQL/DBML

From the publisher

Documentation

sqemo-mcp

MCP server for Sqemo — AI agents that follow your team's database naming standard.

{ "mcpServers": { "sqemo": { "command": "npx", "args": ["-y", "sqemo-mcp"] } } }

Works with Claude Code, Claude Desktop, Cursor, and any MCP client. Local .erd.json files need no account; cloud ERDs and Pro tools need npx sqemo-mcp login.

What it looks like

Model a discussion board where members post articles, a post can be a reply to another post, and members comment on posts.

The agent calls the tools with logical names and never types a column name:

upsert_entity    { logicalName: "Post" }
// → { physicalName: "POST" }

upsert_attribute { logicalName: "Post Content", domain: "Content" }
// → { physicalName: "POST_CNTS" }          // Content → CNTS: from the team word list

upsert_attribute { logicalName: "Delete Flag", domain: "Flag" }
// → { physicalName: "DELETE_YN" }          // Flag → YN: same rule in every table

lint_erd
// → naming drift, missing words, referential integrity — before any DDL is written

Full walkthrough with every tool call: Describe the work, get a governed schema.

Overview

npm: sqemo-mcp
Official MCP Registry: io.github.sqemo/sqemo
Web app: app.sqemo.com

Requires Node.js >= 22. Local-file tools work without any account or configuration. Login is needed for cloud ERD tools, and for the tools marked (Pro) below.

Installation

Claude Code (`.mcp.json`)

{
  "mcpServers": {
    "sqemo": { "command": "npx", "args": ["-y", "sqemo-mcp"] }
  }
}

Claude Desktop

Add the same mcpServers entry to your config file:

Windows: %APPDATA%\Claude\claude_desktop_config.json
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Cursor (`.cursor/mcp.json`)

{
  "mcpServers": {
    "sqemo": { "command": "npx", "args": ["-y", "sqemo-mcp"] }
  }
}

Login (cloud ERDs and Pro tools)

npx sqemo-mcp login    # pick Google, GitHub, or email + password
npx sqemo-mcp logout   # removes stored credentials

Credentials are stored in ~/.erdmaker/credentials.json (mode 0600 on POSIX); your password is never persisted.
Non-interactive shortcuts: --password forces the email + password path, --provider google|github forces a browser path.
Piped input skips the menu and goes straight to email + password, so existing automation keeps working: printf 'email\npassword\n' | npx sqemo-mcp login
The browser paths need a browser on the same machine (the callback returns to 127.0.0.1). Over SSH or in CI, use --password or the SQEMO_EMAIL / SQEMO_PASSWORD environment variables.

What you can do

36 tools in total.

Read (17 tools)

Tool	Description
`list_erds` / `list_workspaces`	Cloud ERDs and workspaces you belong to (login required)
`get_erd_overview`	Name, dialect, entity/relationship/domain/glossary stats
`list_entities` / `get_entity`	Entity list and full detail (attributes, keys, logical/physical mapping)
`list_relationships`	Relationships with endpoints and cardinality
`list_domains`	Domain definitions (also from workspace standard glossaries)
`search_dictionary`	Search the team glossary (logical/physical words, abbreviations, synonyms)
`check_naming`	Check a logical name against the team naming standard
`generate_physical_name`	Logical name → physical name via glossary + naming rules
`export_sql`	CREATE TABLE SQL — mysql, postgres, cubrid, oracle, sqlserver, sqlite, h2
`export_dbml`	DBML text
`validate_erd` / `lint_erd`	Structural validation and full lint (naming drift, referential integrity, duplicates)
`diff_erds`	Diff two sources (files, cloud ERDs, or raw SQL/DBML text) — dry-run before imports
`export_alter_sql`	Migration (ALTER) script from the physical diff against a baseline — renames stay renames via stable IDs, destructive changes come commented out (Pro)
`list_proposals`	Glossary proposal queue status (login required)

Live database (2 tools)

Read-only against your own database. Both query only the information schema — never table data — and the connection URL is used by this local process only, never sent to Sqemo servers.

Tool	Description
`introspect_db`	Import a live PostgreSQL/MySQL schema into an existing ERD (Pro)
`check_db_drift`	Check a live database or a schema dump against the ERD's physical model — missing/extra tables and columns, PK/FK/NOT NULL mismatches (Pro)

Write (17 tools)

Tool	Description
`create_erd`	New ERD from scratch or from SQL/DBML text — to a file or the cloud
`upsert_entity` / `delete_entity`	Entity editing with automatic physical-name derivation
`upsert_attribute` / `delete_attribute`	Attribute editing — PK rules and FK propagation handled automatically
`upsert_relationship` / `delete_relationship`	Relationship editing with automatic FK derivation
`upsert_domain` / `delete_domain`	Domain definition editing
`upsert_dictionary_word` / `delete_dictionary_word`	Glossary editing (standard-linked glossaries are protected)
`update_naming_rules`	Naming rule editing (delimiter, case, unknown-word handling)
`import_sql` / `import_dbml`	Replace an ERD from parsed SQL/DBML (IDs preserved)
`auto_layout`	Automatic entity/table layout (dagre)
`propose_dictionary_word` / `withdraw_proposal`	Propose new glossary words for owner approval

Cloud writes require owner or shared-editor permission and are protected by version CAS with 3-way auto-merge for concurrent edits.

CLI for CI pipelines

Offline, file-based subcommands (no login needed):

# Naming-standard check — exits 1 on violations, great as a CI gate
npx sqemo-mcp lint schema.erd.json

# Schema export to stdout
npx sqemo-mcp export schema.erd.json --format sql --dialect postgres > schema.sql
npx sqemo-mcp export schema.erd.json --format dbml > schema.dbml

Drift mode compares the model against a real database or a dump, and exits 1 when they disagree (Pro, requires login):

npx sqemo-mcp lint schema.erd.json --db "$DATABASE_URL" [--db-schema public] [--strict]
npx sqemo-mcp lint schema.erd.json --schema dump.sql --dialect postgres
npx sqemo-mcp lint --erd <cloud-erd-id> --db "$DATABASE_URL" --ignore 'tmp_*'

GitHub Actions example:

- run: npx sqemo-mcp lint schema.erd.json
- run: npx sqemo-mcp lint schema.erd.json --db "${{ secrets.DATABASE_URL }}"

Environment variables

Variable	Purpose
`SQEMO_EMAIL` / `SQEMO_PASSWORD`	Non-interactive login for CI and SSH sessions (no browser needed)
`ERDMAKER_HOME`	Override the credentials directory (default `~/.erdmaker`)
`ERDMAKER_SUPABASE_URL`	Override the API URL (defaults to the Sqemo cloud)
`ERDMAKER_SUPABASE_ANON_KEY`	Override the API publishable key
`ERDMAKER_MAX_REQUESTS_PER_MINUTE`	Per-minute request cap (default `120`, `0` disables)
`ERDMAKER_MAX_REQUESTS_PER_DAY`	Daily request cap (default `10000`, `0` disables)

The request caps are a safety net against agents stuck in loops; exceeding them returns a rate_limited error that tells the agent to stop and notify the user.

Errors

All tool errors return { code, message } — e.g. not_authenticated, no_permission, save_conflict (retry after re-reading), validation_failed, rate_limited.

License

MIT

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Sqemo?

Does Sqemo need an API key?

What transport does Sqemo use?

When was Sqemo last checked?

Documentation

sqemo-mcp

What it looks like

Overview

Installation

Claude Code (.mcp.json)

Claude Desktop

Cursor (.cursor/mcp.json)

Login (cloud ERDs and Pro tools)

What you can do

Read (17 tools)

Live database (2 tools)

Write (17 tools)

CLI for CI pipelines

Environment variables

Errors

Links

License

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Sqemo?

Does Sqemo need an API key?

What transport does Sqemo use?

When was Sqemo last checked?

Documentation

sqemo-mcp

What it looks like

Overview

Installation

Claude Code (.mcp.json)

Claude Desktop

Cursor (.cursor/mcp.json)

Login (cloud ERDs and Pro tools)

What you can do

Read (17 tools)

Live database (2 tools)

Write (17 tools)

CLI for CI pipelines

Environment variables

Errors

Links

License

Claude Code (`.mcp.json`)

Cursor (`.cursor/mcp.json`)

Claude Code (`.mcp.json`)

Cursor (`.cursor/mcp.json`)