Failed to start multiple MCP tools using the config file #11

Closed
opened 2026-02-15 20:17:24 -05:00 by yindo · 8 comments
Owner

Originally created by @yidecode on GitHub (Apr 2, 2025).

The configuration file data is as follows:

{
    "mcpServers": {
        "memory": {
            "command": "npx",
            "args": [
                "-y",
                "@modelcontextprotocol/server-memory"
            ]
        },
        "time": {
            "command": "uvx",
            "args": [
                "mcp-server-time",
                "--local-timezone=America/New_York"
            ]
        }
    }
}

start command

mcpo --port 18000 --config config.json

Image

Image

Originally created by @yidecode on GitHub (Apr 2, 2025). The configuration file data is as follows: ```json { "mcpServers": { "memory": { "command": "npx", "args": [ "-y", "@modelcontextprotocol/server-memory" ] }, "time": { "command": "uvx", "args": [ "mcp-server-time", "--local-timezone=America/New_York" ] } } } ``` start command ```shell mcpo --port 18000 --config config.json ``` ![Image](https://github.com/user-attachments/assets/60848881-8835-4043-8a6c-3b1174a98eb0) ![Image](https://github.com/user-attachments/assets/592bab20-ba17-4838-a14e-aa13e777ef50)
yindo closed this issue 2026-02-15 20:17:24 -05:00
Author
Owner

@iamdaveloper commented on GitHub (Apr 2, 2025):

try to curl http://127.0.0.1:18000/memory/openapi.json or ......./time/openapi.json

@iamdaveloper commented on GitHub (Apr 2, 2025): try to curl `http://127.0.0.1:18000/memory/openapi.json` or `......./time/openapi.json`
Author
Owner

@agreatfool commented on GitHub (Apr 2, 2025):

try to curl http://127.0.0.1:18000/memory/openapi.json or ......./time/openapi.json

I think the purpose of provide a config file with all the mcp tools inside is to let the server help to merge all the information together to give a complete API list. No?

@agreatfool commented on GitHub (Apr 2, 2025): > try to curl `http://127.0.0.1:18000/memory/openapi.json` or `......./time/openapi.json` I think the purpose of provide a config file with all the mcp tools inside is to let the server help to merge all the information together to give a complete API list. No?
Author
Owner

@agreatfool commented on GitHub (Apr 2, 2025):

This is what I got by using mcpo

Image

Image

Image

Image

Image

Image

@agreatfool commented on GitHub (Apr 2, 2025): This is what I got by using `mcpo` ![Image](https://github.com/user-attachments/assets/025a8485-335d-4b92-8b7c-0b09d2ccf320) ![Image](https://github.com/user-attachments/assets/5fc5a587-e193-4e5f-a8ce-224287e9a899) ![Image](https://github.com/user-attachments/assets/581346f2-db1a-4ff0-97e2-008abef4cc8a) ![Image](https://github.com/user-attachments/assets/f8ab2e8c-d6e8-4bed-a1ca-e16a160c0c11) ![Image](https://github.com/user-attachments/assets/0411d76c-ee3c-49d1-bd3e-ce64f07ae71d) ![Image](https://github.com/user-attachments/assets/7a333b5e-2574-49ba-a6ae-e8261d0a4d97)
Author
Owner

@agreatfool commented on GitHub (Apr 2, 2025):

Maybe this is the correct behavior what is designed at the beginning, though I don't think it make sense. Better to have all the tools merged to one endpoint by mcpo which could be input in the webui tool config, rather than manually input lots of urls in the config panel one by one.

@agreatfool commented on GitHub (Apr 2, 2025): Maybe this is the correct behavior what is designed at the beginning, though I don't think it make sense. Better to have all the tools merged to one endpoint by mcpo which could be input in the webui tool config, rather than manually input lots of urls in the config panel one by one.
Author
Owner

@peanutsugarlove commented on GitHub (Apr 2, 2025):

You need to give the name of the parameter separately, which is http://127.0.0.1:18000/memory,http://127.0.0.1:18000/time

@peanutsugarlove commented on GitHub (Apr 2, 2025): You need to give the name of the parameter separately, which is http://127.0.0.1:18000/memory,http://127.0.0.1:18000/time
Author
Owner

@iamdaveloper commented on GitHub (Apr 2, 2025):

Maybe this is the correct behavior what is designed at the beginning, though I don't think it make sense. Better to have all the tools merged to one endpoint by mcpo which could be input in the webui tool config, rather than manually input lots of urls in the config panel one by one.

In my cases, input it one by one is suit for us, as differnet users can add different tools

@iamdaveloper commented on GitHub (Apr 2, 2025): > Maybe this is the correct behavior what is designed at the beginning, though I don't think it make sense. Better to have all the tools merged to one endpoint by mcpo which could be input in the webui tool config, rather than manually input lots of urls in the config panel one by one. In my cases, input it one by one is suit for us, as differnet users can add different tools
Author
Owner

@agreatfool commented on GitHub (Apr 2, 2025):

In my cases, input it one by one is suit for us, as differnet users can add different tools

Yeah, different use cases. It's good to have an option to control it. For personal using, or small groups, they may want to have everything they have on the list with single input, quick and easy.

@agreatfool commented on GitHub (Apr 2, 2025): > In my cases, input it one by one is suit for us, as differnet users can add different tools Yeah, different use cases. It's good to have an option to control it. For personal using, or small groups, they may want to have everything they have on the list with single input, quick and easy.
Author
Owner

@dahetaoa commented on GitHub (Apr 2, 2025):

也许这就是一开始设计的正确行为,尽管我认为这没有意义。最好通过 mcpo 将所有工具合并到一个端点,可以在 webui 工具配置中输入,而不是在配置面板中手动输入大量 url。

同意,mcpo的意义本就该是这样,不然还不如直接原生支持mcp

@dahetaoa commented on GitHub (Apr 2, 2025): > 也许这就是一开始设计的正确行为,尽管我认为这没有意义。最好通过 mcpo 将所有工具合并到一个端点,可以在 webui 工具配置中输入,而不是在配置面板中手动输入大量 url。 同意,mcpo的意义本就该是这样,不然还不如直接原生支持mcp
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: open-webui/mcpo#11