MCP Atlas
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| migrate-applyC | Apply pending migration files to a database |
| migrate-diffB | Generate a new migration file by comparing current state to desired schema |
| migrate-lintC | Run analysis on migration directory to detect issues |
| migrate-newB | Create a new empty migration file in the migration directory |
| migrate-statusC | Report current migration status of a database |
| migrate-validateB | Validate migration directory integrity and consistency |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
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.
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.
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.
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.