Hello,
I’m the Product Manager at COROS in charge of the MCP module.
Thank you very much for your feedback. We have received your issue report and reviewed its content. We’ve determined the core root cause is a routing problem.
This GitHub project essentially replicates the functionality built into our official skill (installed via npm install -g coros-mcp). It does not enable users to connect to COROS MCP via OpenAI directly; instead, it routes users to the corresponding COROS MCP endpoint based on their IP address. For users located in Europe, it establishes a direct connection to the EU MCP server.
The actual unresolved question is: why the MCP service fails to connect successfully within Codex. We find this perplexing, as all our internal testing has gone smoothly. That said, we do occasionally receive reports of such connection failures.
Could you please share more details to help us troubleshoot and pinpoint the exact issue?
email：xuzhixiang@coros.com
Hello,
I’m the Product Manager at COROS in charge of the MCP module.
Thank you very much for your feedback. We have received your issue report and reviewed its content. We’ve determined the core root cause is a routing problem.
This GitHub project essentially replicates the functionality built into our official skill (installed via npm install -g coros-mcp). It does not enable users to connect to COROS MCP via OpenAI directly; instead, it routes users to the corresponding COROS MCP endpoint based on their IP address. For users located in Europe, it establishes a direct connection to the EU MCP server.
The actual unresolved question is: why the MCP service fails to connect successfully within Codex. We find this perplexing, as all our internal testing has gone smoothly. That said, we do occasionally receive reports of such connection failures.
Could you please share more details to help us troubleshoot and pinpoint the exact issue?
email：xuzhixiang@coros.com