MCP Apps: Rohlik cart buttons fail and require extra confirmations compared with ChatGPT #29266

Problem

I use the Rohlik MCP server documented at https://www.rohlik.cz/mcp-docs (endpoint: https://mcp.rohlik.cz/mcp), accessed through the connected Rohlik app in Codex.

In ChatGPT, clicking Add to cart in the product widget works without an additional confirmation popup in my usage.

In T3 Code, the button initially showed “Something went wrong” without adding the product. Local tool-name translation made tested product cards work, but T3 still asks for confirmation. Newly generated cards can fail again unless patched.

Environment

• Codex integration, with Rohlik exposed through codex_apps.
• T3 server/runtime 0.1.5 in a Linux sandbox, accessed from desktop and native Android.
• Android app 2.2.0; exact desktop and OS versions were not recorded.
• The latest unmodified release has not yet been tested.

Reproduction

1. Connect Rohlik through Codex in T3 Code.
2. Ask for native product cards for yogurt.
3. Click Add to cart, approving any confirmation if shown.
4. Read the live cart separately to verify the result before retrying.

Findings

The widget requested add_items_to_cart / update_cart_item, while the provider catalog exposed rohlik.add_items_to_cart / rohlik.update_cart_item.

Translating these names in saved widget HTML was followed by successful additions verified against the live cart. The installed desktop and mobile clients were not modified. Mobile failures later recurred; this workaround is not a verified permanent fix.

Expected behavior

Product and cart widgets should work without local patches, consistently on macOS and Android.

Could tool-name compatibility be fixed generally in T3's integration, or should it be corrected in the Rohlik widget?

Separately, I would like the same interaction I observe in ChatGPT, without repeated confirmation popups after clicking a widget button. Could T3 provide generic, user-configurable permissions for MCP widgets, such as ask every time, allow for this session, or remember permission? I am happy to move this proposal to an Ideas discussion.

The naming problem and confirmation policy are separate: we have not established that confirmation caused the failed additions.