ezmd MCP Server

What the code does

We read the source, 1 d ago · rules 995398eba69f

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

            r"(you (must|should|will|need to) |please |now )(run|execute|type) (`|\")?(rm -rf|sudo|curl|wget|cat /etc)",

                probe = subprocess.run(  # noqa: S603 - fixed argv

            target.lstrip("/") if target.startswith("/") else posixpath.normpath(posixpath.join(base_dir, target))

      for p in package.json pnpm-lock.yaml pnpm-workspace.yaml .npmrc apps/web apps/extension packages/sdk-ts docs/api; do \

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add ezmd -- uvx ezmd-mcp

{
  "mcpServers": {
    "ezmd": {
      "command": "uvx",
      "args": [
        "ezmd-mcp"
      ]
    }
  }
}

[mcp_servers.ezmd]
command = "uvx"
args = ["ezmd-mcp"]

{
  "mcpServers": {
    "ezmd": {
      "command": "uvx",
      "args": [
        "ezmd-mcp"
      ]
    }
  }
}

{
  "servers": {
    "ezmd": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "ezmd-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: EZMD_PROFILE (Default output profile: full, compact, rag or agent), EZMD_MCP_ALLOWED_DIRS (Directories convert_file may read, separated by the OS path separator (default: working directory)), EZMD_REMOTE (Base URL of an ezmd instance; converts there instead of in-process), EZMD_API_KEY (API key for EZMD_REMOTE, sent as X-API-Key).