Skip to main content
Glama
Sign In
MCP Atlas

MCP Atlas

by mpreziuso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

MCP Atlas

An MCP (Model Context Protocol) server for Ariga Atlas, enabling AI assistants to interact with Atlas migration tools through the Model Context Protocol.

What is this?

This package provides a bridge between AI assistants (like Claude) and Atlas, allowing them to manage database migrations, validate schemas, and perform other database-related operations using Atlas commands.

Related MCP server: Vanna AI MCP Server

Features

  • migrate-apply: Apply pending migration files to a database

  • migrate-diff: Generate new migration files by comparing current state to desired schema

  • migrate-lint: Run analysis on migration directory to detect issues

  • migrate-new: Create new empty migration files

  • migrate-status: Report current migration status of a database

  • migrate-validate: Validate migration directory integrity and consistency

Prerequisites

  • Atlas CLI must be installed and available in your PATH

  • Node.js 18 or higher

Configuration

Add this server to your MCP client configuration. For Claude Desktop, add to your config file:

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

{
  "mcpServers": {
    "atlas": {
      "command": "npx",
      "args": ["-y", "@mpreziuso/mcp-atlas"]
    }
  }
}

The -y flag automatically installs or updates the package without prompting.

Usage

Once configured, your AI assistant can use Atlas commands through the MCP protocol. Example interactions:

  • "Check the migration status of my database"

  • "Create a new migration file"

  • "Apply pending migrations to the database"

  • "Validate the migration directory"

  • "Generate a migration diff from my schema"

Example Commands

The MCP server wraps these Atlas CLI commands:

  • atlas migrate apply - Apply migrations

  • atlas migrate diff - Generate migration diffs

  • atlas migrate lint - Lint migration files

  • atlas migrate new - Create new migration

  • atlas migrate status - Check migration status

  • atlas migrate validate - Validate migrations

License

MIT

Author

Michele Preziuso mpreziuso@kaosdynamics.com

Repository

https://github.com/mpreziuso/mcp-atlas

Available Tools

6 tools
migrate-applyC

Apply pending migration files to a database

Inputs: url (required), dirUrl, dryRun, txMode, +3 more.

migrate-diffB

Generate a new migration file by comparing current state to desired schema

Inputs: to (required), devUrl, dirUrl, name, +2 more.

migrate-lintC

Run analysis on migration directory to detect issues

Inputs: dirUrl (required), devUrl, latest, gitBase, +1 more.

migrate-newB

Create a new empty migration file in the migration directory

Inputs: dirUrl (required), name, edit.

migrate-statusC

Report current migration status of a database

Inputs: url (required), dirUrl, format.

migrate-validateB

Validate migration directory integrity and consistency

Inputs: dirUrl (required), devUrl, format.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.6/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose within the migration workflow: apply, diff, lint, new, status, and validate. The descriptions specify unique actions (e.g., applying migrations vs. generating diffs vs. detecting issues), leaving no ambiguity about which tool to use for a given task.

    Naming Consistency5/5

    All tools follow a consistent 'migrate-verb' pattern with hyphenated naming (e.g., migrate-apply, migrate-diff). This predictable structure makes it easy to understand each tool's function and ensures uniformity across the set.

    Tool Count5/5

    With 6 tools, the server is well-scoped for database migration management. Each tool serves a specific, non-redundant role in the migration lifecycle, from creation to validation and application, making the count appropriate and efficient for the domain.

    Completeness5/5

    The toolset provides complete coverage of the migration domain, including creation (migrate-new), analysis (migrate-diff, migrate-lint, migrate-validate), status tracking (migrate-status), and execution (migrate-apply). There are no obvious gaps, enabling agents to handle the full migration workflow without dead ends.

    Resources

    Related MCP Connectors

    Related MCP Servers

    • Vanna AI MCP Server

      lilgreml1n
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that allows AI assistants to query databases using natural language by leveraging Vanna AI. It supports secure SSH tunneling, model training on database schemas, and persistent storage of SQL patterns via ChromaDB.
      2
      -

    • instant-db

      urbushey
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to create and manage persistent SQLite databases through natural language without requiring SQL knowledge. It allows users to propose schemas, store records, and perform complex queries across multiple databases for structured data tracking.
      MIT

    • Database MCP Server

      roilanrodriguez55
      A
      license
      Not graded
      quality
      D
      maintenance
      An extensible MCP server for database operations that supports PostgreSQL for managing schemas, tables, data, and user permissions. It features automatic migration recording for DDL changes and integrates with various AI-powered editors like Cursor, Zed, and Claude Code.
      24 npm
      2
      MIT