DBMigratePro Migrations

io.github.provydonPublished by GitHub account provydonv1.0.0Updated Oct 24, 2026

Move a database between providers, or convert MySQL to PostgreSQL, with integrity verified.

VerifiedStreamable HTTPWeb executableDatabases

Overview

AI-generated overview

Lets an assistant move a database between providers or convert MySQL to PostgreSQL through DBMigratePro, with integrity verified.

What you can do
DBMigratePro Migrations is a remote MCP server that connects an assistant to the DBMigratePro migration service. According to the registry description, it lets the assistant move a database between providers or convert MySQL to PostgreSQL, with integrity verified. The manifest lists no individual tools, so the exact operations available are not documented here.
When to use it
Useful when you want an assistant to help carry out a database migration between providers or a MySQL-to-PostgreSQL conversion, and you already use DBMigratePro. It is not aimed at routine querying or administration of a database.
Requirements
A remote endpoint at dbmigratepro.com over streamable HTTP. A DBMigratePro API token is required, created under Settings, API Tokens, and sent in the Authorization header. No local runtime, packages or environment variables are declared.
Before you install
The server requires a DBMigratePro API token in the Authorization header; the manifest notes it can be scoped to the mcp:migrations ability to limit the server to migrations. Migration operations can change or move production data, so review scope and targets before use. No payment, wallet or third-party data-sharing details are shown.

Installation

In SourceWeft

  1. Open DBMigratePro Migrations in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.provydon%2Fdbmigratepro-migrations/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "dbmigratepro-migrations": {
      "type": "http",
      "url": "https://dbmigratepro.com/mcp-migrations",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.