DBMigratePro Continuous Migration

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

Keep a target database continuously in sync with a source on another provider, then promote it.

VerifiedStreamable HTTPWeb executableDatabasesCloud & Infrastructure

Overview

AI-generated overview

A remote DBMigratePro server that lets an assistant keep a target database continuously in sync with a source on another provider, then promote it.

What you can do
Keep a target database continuously synchronized with a source database hosted on another provider, then promote the target. Access is authenticated with a DBMigratePro API token, which can be scoped to the continuous migration ability. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when you are running a cross-provider database migration and want an assistant to manage ongoing replication and the final cutover to the target.
Requirements
A remote endpoint at dbmigratepro.com over streamable HTTP. A DBMigratePro account and an API token created under Settings -> API Tokens, sent as a bearer token in the Authorization header. No local runtime or packages are needed.
Before you install
The server requires a DBMigratePro API token in the Authorization header; scope it to the mcp:replicas ability if you want it limited to continuous migration. It can change database state by syncing and promoting a target database, so verify which source and target are involved before use.

Installation

In SourceWeft

  1. Open DBMigratePro Continuous Migration 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-continuous-migration/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-continuous-migration": {
      "type": "http",
      "url": "https://dbmigratepro.com/mcp-replicas",
      "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.