sqemo/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.
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:
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)
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)
Login (cloud ERDs and Pro tools)
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) |