open-webui/mcpo

Fork 0

mirror of https://github.com/open-webui/mcpo.git synced 2026-11-05 01:27:39 +00:00

[GH-ISSUE #57] issue: toplevel `openapi.json` content is wrong #27

New issue

Closed

opened 2026-10-18 21:10:31 +00:00 by bsakaguchi · 3 comments

bsakaguchi commented

2026-10-18 21:10:31 +00:00

Owner

Originally created by @geiseri on GitHub (Apr 8, 2025).
Original GitHub issue: https://github.com/open-webui/mcpo/issues/57

Check Existing Issues

I have searched the existing issues and discussions.
I am using the latest version of mcpo.

mcpo Version

commit v0.0.9

Open WebUI Version (if applicable)

No response

Operating System

linux

Browser (if applicable)

No response

Confirmation

I have read and followed all instructions in README.md.
I am using the latest version of both MCPO and Open WebUI.
I have included the browser console logs.
I have included the Docker container logs.
I have listed steps to reproduce the bug in detail.

Expected Behavior

curl http://mcp:8181/openapi.json | jq .

{
  "openapi": "3.1.0",
  "info": {
    "title": "MCP OpenAPI Proxy",
    "description": "Automatically generated API from MCP Tool Schemas\n\n- **available tools**：    - [time](http://mcp:8181/time/docs)\n    - [calculator](http://mcp:8181/calculator/docs)\n",
    "version": "1.0"
  },
  "paths": {}
}

Actual Behavior

curl http://mcp:8181/openapi.json

{
  "openapi": "3.1.0",
  "info": {
    "title": "MCP OpenAPI Proxy",
    "description": "Automatically generated API from MCP Tool Schemas\n\n- **available tools**：    - [time](http://0.0.0.0:8181/time/docs)\n    - [calculator](http://0.0.0.0:8181/calculator/docs)\n",
    "version": "1.0"
  },
  "paths": {}
}

Steps to Reproduce

Use curl or a similar tool to access the openapi.json endpoint

Logs & Screenshots

The proxy correctly shows that the endpoint had been accessed.

mcptool_1             | INFO:     10.0.12.21:51217 - "GET /openapi.json HTTP/1.1" 200 OK

Additional Information

No response

Originally created by @geiseri on GitHub (Apr 8, 2025). Original GitHub issue: https://github.com/open-webui/mcpo/issues/57 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of mcpo. ### mcpo Version commit v0.0.9 ### Open WebUI Version (if applicable) _No response_ ### Operating System linux ### Browser (if applicable) _No response_ ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** MCPO and Open WebUI. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have listed steps to reproduce the bug in detail. ### Expected Behavior ``` curl http://mcp:8181/openapi.json | jq . ``` ``` { "openapi": "3.1.0", "info": { "title": "MCP OpenAPI Proxy", "description": "Automatically generated API from MCP Tool Schemas\n\n- **available tools**： - [time](http://mcp:8181/time/docs)\n - [calculator](http://mcp:8181/calculator/docs)\n", "version": "1.0" }, "paths": {} } ``` ### Actual Behavior ``` curl http://mcp:8181/openapi.json ``` ``` { "openapi": "3.1.0", "info": { "title": "MCP OpenAPI Proxy", "description": "Automatically generated API from MCP Tool Schemas\n\n- **available tools**： - [time](http://0.0.0.0:8181/time/docs)\n - [calculator](http://0.0.0.0:8181/calculator/docs)\n", "version": "1.0" }, "paths": {} } ``` ### Steps to Reproduce Use `curl` or a similar tool to access the `openapi.json` endpoint ### Logs & Screenshots The proxy correctly shows that the endpoint had been accessed. ``` mcptool_1 | INFO: 10.0.12.21:51217 - "GET /openapi.json HTTP/1.1" 200 OK ``` ### Additional Information _No response_

bsakaguchi

2026-10-18 21:10:31 +00:00

closed this issue
added the
bug
label

bsakaguchi commented

2026-10-18 21:10:32 +00:00

Author

Owner

@tjbck commented on GitHub (Apr 8, 2025):

Intended behaviour but PR welcome.

@tjbck commented on GitHub (Apr 8, 2025): Intended behaviour but PR welcome.

bsakaguchi commented

2026-10-18 21:10:32 +00:00

Author

Owner

@westtexasfish commented on GitHub (Apr 8, 2025):

First I'd like to say thank you so much for your work. I too found this intended behavior strange. I am just a hobbyist and nowhere near confident enough in my abilities or even in Github collaboration to do any kind of PR. I managed, (with Cline's assistance) to chop in a "--hostname" command option along with the further required edits to achieve the @geiseri - Expected Behavior above. Like I say, I'm sure your reasoning is solid, and adheres to the OpenAPI standard. I'm just voicing the confusion of an amateur haha. Thanks again!

@westtexasfish commented on GitHub (Apr 8, 2025): First I'd like to say thank you so much for your work. I too found this intended behavior strange. I am just a hobbyist and nowhere near confident enough in my abilities or even in Github collaboration to do any kind of PR. I managed, (with Cline's assistance) to chop in a "--hostname" command option along with the further required edits to achieve the @geiseri - Expected Behavior above. Like I say, I'm sure your reasoning is solid, and adheres to the OpenAPI standard. I'm just voicing the confusion of an amateur haha. Thanks again!

bsakaguchi commented

2026-10-18 21:10:33 +00:00

Author

Owner

@tjbck commented on GitHub (Apr 9, 2025):

Addressed with 292059ee5e

@tjbck commented on GitHub (Apr 9, 2025): Addressed with 292059ee5e3aaf7455c2f972e3923feee0439318

bsakaguchi referenced this issue

2026-10-18 21:12:13 +00:00

[PR #27] [MERGED] doc: readme #146

bsakaguchi referenced this issue

2026-10-18 21:12:16 +00:00