Db Metadata Extractor MCP

Db Metadata Extractor MCP runs locally from a Python package published to PyPI: db-metadata-extractor-mcp version 0.1.6. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx db-metadata-extractor-mcp; the entry names python as the runtime.

Db Metadata Extractor MCP runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: docker.io/optisolbusinesssol/db-metadata-extractor-mcp:0.1.6. 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/optisolbusinesssol/db-metadata-extractor-mcp:0.1.6.

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

{
  "mcpServers": {
    "db-metadata-extractor-mcp": {
      "command": "uvx",
      "args": [
        "db-metadata-extractor-mcp"
      ]
    }
  }
}

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