This page covers the command and args fields inside the flyway entry of your .mcp.json—see Setup if you haven't created that file yet.

{
  "mcpServers": {
    "flyway": {
      "type": "stdio",
      "command": "<path to flyway>",
      "args": [
        "mcp",
        "-mcp.toolsets=develop_migrations",
        "-mcp.maxLogs=100"
      ]
    }
  }
}

Command flag in .mcp.json

Set command to your flyway executable. If you installed Flyway following the standard installation instructions, flyway is added to your system PATH, so command: "flyway" is enough—the AI tool runs it just like you would from a terminal.

Use the full path instead (e.g. C:\flyway-{version}\flyway.cmd or /opt/flyway-{version}/flyway) if:

• flyway isn't on your PATH, or
• your AI tool is launched from a desktop shortcut rather than a terminal—some GUI-launched apps don't inherit your shell's PATH, particularly on macOS.

On Windows, if you do use a bare flyway and it isn't picked up, try flyway.cmd explicitly—some process launchers don't resolve a bare command name to its .cmd extension the way a terminal does.

The args list in .mcp.json

Configuration can be set in the args list in .mcp.json, as shown by the -mcp.toolsets setting in the example above.

Toolsets in .mcp.json

Toolsets allow you to configure which Tools you're happy for the Flyway MCP server to use with your prompts. See Tool reference for the list of tools each toolset enables.

mcp.toolsets has no default. You must explicitly configure at least one, or the server will fail to start. To enable more than one, separate them with commas, e.g. -mcp.toolsets=develop_migrations,develop_state.