MigraFlow - Database Migration AI

io.github.wmeirelesPublished by GitHub account wmeirelesv1.0.1Updated Oct 24, 2026

AI-powered database migration. Analyze schemas, generate SQL, calculate risks.

VerifiedSTDIODesktop onlyDatabasesDeveloper Tools

Overview

AI-generated overview

MigraFlow is a local MCP server that lets an assistant analyze database schemas, generate migration SQL and assess migration risks through the MigraFlow API.

What you can do
Analyze database schemas for migration planning, as described for the MigraFlow service (no individual tools are listed). Generate SQL for database migrations. Calculate and report migration risks. All work is performed through the MigraFlow API rather than locally.
When to use it
Useful when planning a database migration and you want an assistant to inspect schemas, draft migration SQL and surface risks before changes are applied. It suits teams already using or evaluating the MigraFlow service.
Requirements
Runs as a local process installed from the PyPI package migraflow-mcp (Python runtime needed). Requires a MigraFlow Enterprise API key supplied in the MIGRAFLOW_API_KEY environment variable. The API endpoint defaults to the MigraFlow service and can be overridden with MIGRAFLOW_API_URL. Network access to the API is required. Desktop only.
Before you install
The API key is a secret sent to the MigraFlow service; keep it out of shared configuration. Schema details and generated SQL are sent to a third-party API, so consider whether that data is sensitive. Review generated migration SQL before running it against a real database.

Installation

In SourceWeft

  1. Open MigraFlow - Database Migration AI in the dashboard and add it to a workspace.
  2. 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

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

25% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.