DBConvert Streams (Federated SQL)

DBConvert Streams (Federated SQL) runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/slotix/dbconvert-streams-public/releases/download/v2.7.3/dbconvert-streams-2.7.3.mcpb version 2.7.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.

DBConvert Streams (Federated SQL) runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: docker.io/slotix/stream-mcp:2.7.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm docker.io/slotix/stream-mcp:2.7.3.

DBConvert Streams (Federated SQL) runs locally from a Node.js package published to the npm registry: @dbconvert/stream-mcp version 2.7.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @dbconvert/stream-mcp@2.7.3.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "streams": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "docker.io/slotix/stream-mcp:2.7.3"
      ]
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect