Skip to main content
Glama
wabox32

schema-engram-mcp

by wabox32
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
sqliteNoPath to the SQLite file, specified via the --sqlite command-line argument. Defaults to ~/.local/share/schema-engram-mcp/schemas.sqlite if not provided.
SCHEMA_ENGRAM_SQLITENoPath to the SQLite file. This environment variable has priority over the --sqlite command-line argument.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
db_schema_saveA

Guarda una instantánea del esquema de una base de datos.

schema debe ser un objeto JSON con la estructura que quieras persistir (por ejemplo tablas con columnas, tipos, nullability, PK/FK e índices).

Args: workspace_id: Identificador del proyecto o carpeta (p. ej. nombre del repo). connection_name: Nombre lógico de la BD (p. ej. local, staging, prod). schema: Objeto o texto JSON con el esquema. dialect: Opcional: postgresql, mysql, sqlite, etc. label: Etiqueta opcional (p. ej. versión de migración). summary: Nota corta opcional.

db_schema_getB

Obtiene un esquema guardado. Si snapshot_id es None, devuelve el más reciente para workspace_id + connection_name.

db_schema_listC

Lista instantáneas guardadas (sin el cuerpo completo del esquema).

db_schema_updateA

Actualiza una instantánea existente. Debes indicar el mismo workspace_id y connection_name que tenía el registro (sirven como comprobación).

Los argumentos opcionales con valor por defecto en el cliente no aplican cambios salvo que los envíes: schema sustituye el JSON completo; dialect, label y summary solo se escriben si los pasas (cadena vacía → NULL en BD).

new_workspace_id / new_connection_name renombran la instantánea si se indican. Con bump_captured_at=true (por defecto) se actualiza la fecha de la fila.

db_schema_deleteB

Elimina una instantánea por id.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: delete removes a snapshot, get retrieves one, list shows metadata without full schema, save creates a new snapshot, and update modifies an existing one. The operations map cleanly to CRUD lifecycle stages with no overlap or ambiguity.

Naming Consistency5/5

All tools follow a perfect 'db_schema_' prefix with consistent verb suffixes (delete, get, list, save, update). The naming pattern is uniform across all five tools, making them easily predictable and readable.

Tool Count5/5

With 5 tools, this server is well-scoped for managing database schema snapshots. Each tool serves a clear function in the lifecycle (list, get, save, update, delete), and no tool feels redundant or missing for the domain.

Completeness5/5

The tool set provides complete CRUD coverage for schema snapshots: list for discovery, get for retrieval, save for creation, update for modification, and delete for removal. There are no obvious gaps, and the descriptions support full lifecycle management.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources