Docker MCP server only works with two MCP configs

Describe the Bug

I have an MCP server configured through Docker that exposes the server via port 8000. I would like it to just work with the following config:

        "MLB": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "-p",
                "8000:8000",
                "--name",
                "mlb-api-mcp",
                "mlb-api-mcp"
            ]
        },

But this does not work (no tools are exposed). However, if I add a second config with a simple server url (and while the Docker container is running), it DOES work:


        "MLB-local": {
            "url": "http://localhost:8000/mcp/"
        },

Looking at the MCP Logs it just doesn’t seem to find the tools from the Docker container, even though it is starting successfully. I’ve tried adding the "url" parameter to the first config but that doesn’t help.

A potentially related issue: Any console logging statement (print, console.log, etc.) seems to trigger an “error” in the MCP logs that it is not valid JSON. But these are just logs to standard out…why would this trigger an error?

Steps to Reproduce

My MCP server I am trying to set up is available here: GitHub - guillochon/mlb-api-mcp

Expected Behavior

MCP server should work with a single docker config.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.4 (user setup)
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90
Date: 2025-07-10T17:09:01.383Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22631

Does this stop you from using Cursor

No - Cursor works, but with this issue

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.