Positive users praise MCP's custom UI support for agents like Claude as powerful and useful for rendering, while negative users call the support wonky with limited use cases, hard auth, and poor dev cycles.
Based on 13 visible X reactions from 21 accounts; directional sample.
Ask a question below.
Published answers will appear here.
glad that people are finding out about this and you can one-shot this MCPs with @manufact and mcp-use SDK. UI returned from tools are useful for a ton of use cases, we invented user interfaces for a reason! actually during initialization phase of an MCP the client shares its capabilities and so you can adapt the MCP server to return text or UI based on that.
@RhysSullivan @benhylak v cool! will be trying out. imo them being able to render ui for this is i think what people mean when they say they want just chat as their main interface for everything this working in its ideal state would save me from really ever needing to go on other sites
@zeeg makes sense. it's working really well for us, and we haven't found another way to do this human labeling flow. only weird thing was establishing if it's supported or not. our work around was attempting to render ui, and if we don't get the ping, falling back.
@benhylak we've been doing this for months! it's a bit janky to implement, but it's so powerful. blows people's minds when see Claude making images.
@benhylak mostly because the support is wonky and the use cases where its _better_ are fairly limited (e.g. where you truly need a custom widget)
@benhylak Because MCP is cursed. The dev cycle on these is awful Way easier to just use ChatGPT’s new inline visualizations and sites.
today i learned that MCP supports custom UI. it works in codex, claude, and more. why does no one else do this?
@NickADobos can you explain? we had the first working version in an hour. we haven't found any edge cases where it fails.
Positive users praise MCP's custom UI support for agents like Claude as powerful and useful for rendering, while negative users call the support wonky with limited use cases, hard auth, and poor dev cycles.
Based on 13 visible X reactions from 21 accounts; directional sample.
Ask a question below.
Published answers will appear here.