
Migration Map Mcp
io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.2Updated Nov 1, 2026
Find local migration numbering gaps and rollback pairing signals without returning SQL, paths,...
Overview
A local MCP server that inspects database migration filenames and reports numbering gaps, duplicates and rollback pairing signals.
- What you can do
- Inspect a project's migration directory and report numbering gaps and duplicate sequence numbers
- Detect rollback pairing signals when a forward and a rollback-style filename share a sequence
- Return risk signals about the migration map without exposing SQL, source content, migration names or full paths
- Check a project path that must sit inside the configured root directory
- When to use it
- Useful before merging database changes when a migration directory has grown hard to reason about and you want a quick check for numbering gaps, duplicates or missing rollback pairs.
- Requirements
- Runs as a local process over stdio, installed from the npm package; the project path passed to the tool must be inside the MIGRATION_MAP_ROOT directory. No accounts, API keys or headers are declared.
Installation
In SourceWeft
- Open Migration Map Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
migration-map-mcp
Migration Map inspects migration filenames and reports numbering gaps, duplicates, and broad risk signals. It is useful before merging database changes when the migration directory has become hard to reason about.
Quick start
Call inspect_migration_map with a project path inside MIGRATION_MAP_ROOT.
Privacy and limits
The server reads migration filenames only. It reports sequence gaps, duplicate numbers, and pairs a sequence when both a forward filename and a rollback-style filename are present. It does not read SQL, source content, migration names, or full paths. Naming conventions outside the recognized pattern may be missed.
Source: README.md at commit 1078464
Tools
0Version history
2- v1.0.2LatestOct 2, 2026
- v1.0.0Sep 22, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.