Replies: 5 comments 1 reply
-
|
try changing: to: |
Beta Was this translation helpful? Give feedback.
-
|
I actually fixed this with this compose file located here (https://github.com/chaoscode/MCPO) |
Beta Was this translation helpful? Give feedback.
-
|
@adelorenzo-portainer Dear Adeloenzo, thank you for the method you provided. @chaoscode Dear chaoscode, thank you for the additional solution you provided. However, I'm still unclear as to the root cause of this original error. I believe there should be a specific reason for it, and a standard solution. But I am very grateful for the method you provided, thank you very much. log
|
Beta Was this translation helpful? Give feedback.
-
|
On windows try to use full path where ever your path is |
Beta Was this translation helpful? Give feedback.
-
|
@ppblaauw Thank you for your reply. I used absolute paths in the configuration, but it still doesn't work. When I test the connection, it always returns a success 200 OK. |
Beta Was this translation helpful? Give feedback.
-
|
I am glad to share with everyone that I have found a solution. In fact, both of the following configurations return a 200 OK when verifying the connection, and the URLs appear to be the same, but only method 2 works when accessing the tool. method 1 method 2 The URL setting that allows successful access to the tool is highlighted in green.
Thank you again to everyone who participated and replied to this issue. I appreciate your enthusiastic provision of solutions. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Check Existing Issues
mcpo Version
main
Open WebUI Version (if applicable)
v0.6.4
Operating System
Windows、Docker
Browser (if applicable)
Edge
Confirmation
README.md.Expected Behavior
Correctly access Tools in Config
Actual Behavior
The Tool was accessed, but the request processing failed, and the Tool could not be used correctly.
Steps to Reproduce
I have created the docker-compose.yml and config.json, successfully connected them to Openwebui,
and the connection is working. Tools are also shown as enabled in OpenAPI/docs.
Connection to Openwebui returns 200, but when I send a request, Tools shows a 404 error
However, this problem doesn't occur when enabling mcpo without using config.json I want to centralize management in config.json, but it appears to be failing during execution, even though it looks normal.
config.json
docker-compose.yml
services: mcp-server: image: ghcr.io/open-webui/mcpo:main container_name: mcp-server ports: - "9005:8000" volumes: - ./config.json:/path/to/config.json #environment: command: --api-key "Hello" --config /path/to/config.json restart: unless-stoppedCreating MCP separately works normally. Here is the docker-compose.yml that works
services: mcp-fetch: image: ghcr.io/open-webui/mcpo:main container_name: mcp-fetch ports: - "9007:8000" #environment: command: --api-key "Hello" -- uvx mcp-server-fetch restart: unless-stoppedLogs & Screenshots
logs
Additional Information
No response
Beta Was this translation helpful? Give feedback.
All reactions