Skip to main content
ClaudeWave
MCP ServersRegistry oficial0 estrellas0 forksMITActualizado 8d ago
Install in Claude Code / Claude Desktop
Method: NPX · sqemo-mcp
Claude Code CLI
claude mcp add sqemo-mcp -- npx -y sqemo-mcp
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "sqemo-mcp": {
      "command": "npx",
      "args": ["-y", "sqemo-mcp"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Casos de uso

Resumen de MCP Servers

# sqemo-mcp

**MCP server for [Sqemo](https://sqemo.com)** — design ERDs with your team's naming standards.

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

- npm: [`sqemo-mcp`](https://www.npmjs.com/package/sqemo-mcp)
- Official MCP Registry: `io.github.sqemo/sqemo`
- Web app: [app.sqemo.com](https://app.sqemo.com)

> Requires Node.js >= 22. Local-file tools work without any account or configuration —
> login is only needed for cloud ERD tools.

## Installation

### Claude Code (`.mcp.json`)

```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`)

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

## Login (only for cloud ERDs)

```bash
npx sqemo-mcp login    # email + password → stores a refresh token
npx sqemo-mcp logout   # removes stored credentials
```

Credentials are stored in `~/.erdmaker/credentials.json` (mode 0600 on POSIX);
your password is never persisted.

## What you can do

### Read (16 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 |
| `list_proposals` | Glossary proposal queue status (login required) |

### 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

Two offline, file-based subcommands (no login needed):

```bash
# 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
```

GitHub Actions example:

```yaml
- run: npx sqemo-mcp lint schema.erd.json
```

## Environment variables

| Variable | Purpose |
|----------|---------|
| `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`.

## Links

- [Sqemo](https://sqemo.com) — team naming standards + ERD design in the browser
- [sqemo-mcp on npm](https://www.npmjs.com/package/sqemo-mcp)
- Feedback and bug reports: [issues](https://github.com/sqemo/sqemo-mcp/issues) or hello@sqemo.com

## License

[MIT](LICENSE)

Lo que la gente pregunta sobre sqemo-mcp

¿Qué es sqemo/sqemo-mcp?

+

sqemo/sqemo-mcp es mcp servers para el ecosistema de Claude AI con 0 estrellas en GitHub.

¿Cómo se instala sqemo-mcp?

+

Puedes instalar sqemo-mcp clonando el repositorio (https://github.com/sqemo/sqemo-mcp) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar sqemo/sqemo-mcp?

+

sqemo/sqemo-mcp aún no ha sido auditado por nuestro agente de seguridad. Revisa el repositorio original en GitHub antes de usarlo en producción.

¿Quién mantiene sqemo/sqemo-mcp?

+

sqemo/sqemo-mcp es mantenido por sqemo. La última actividad registrada en GitHub es de 8d ago, con 0 issues abiertos.

¿Hay alternativas a sqemo-mcp?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega sqemo-mcp en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: sqemo/sqemo-mcp
[![Featured on ClaudeWave](https://claudewave.com/api/badge/sqemo-sqemo-mcp)](https://claudewave.com/repo/sqemo-sqemo-mcp)
<a href="https://claudewave.com/repo/sqemo-sqemo-mcp"><img src="https://claudewave.com/api/badge/sqemo-sqemo-mcp" alt="Featured on ClaudeWave: sqemo/sqemo-mcp" width="320" height="64" /></a>

Más MCP Servers

Alternativas a sqemo-mcp