Description
When curling the MCP endpoint at http://127.0.0.1:9000/mcp, it returns Service Unavailable, but the BrowserOS MCP service is actually working correctly.
Steps to Reproduce
- Start BrowserOS
- Run:
curl -s http://127.0.0.1:9000/mcp
- Response:
Service Unavailable
Expected Behavior
The MCP endpoint should return a proper response (e.g., MCP server info or a valid JSON response) when the service is running.
Actual Behavior
Returns Service Unavailable even though the service is fully functional.
Evidence
Despite the Service Unavailable response from curl, the MCP tools work correctly:
mcporter call browser-mcp.browser_open_tab url=http://www.baidu.com active=true
# Output: Opened new tab: Untitled
# URL: http://www.baidu.com/
# Tab ID: 1697407683
Environment
- BrowserOS version: latest
- OS: macOS
Suggested Fix
The MCP HTTP endpoint should properly respond to health check requests or provide a valid MCP response instead of returning Service Unavailable when the service is actually running.