Repository navigation
[Enhancement]: Support structuredContent #8450
Replies: 3 comments 1 reply
|
The structured content is for the output of the tool call, and mainly on the MCP server, not the client (LibreChat) to address. It would have to be meaningful for the client to adopt, and I don't see the immediate use case for it in LibreChat. This seems like it would be more useful to pipe into some programmatic workflow, as part of an ETL/ELT script, for example. |
|
Adding a concrete case and a PR, because I think this is narrower than the original ask. Scope first: this isn't asking LibreChat to consume structured output for rich rendering — that's the 2025 request, and I take the point that it's largely the server's concern. This is about not discarding a payload we already have. When a server sends Why the client can't defer to the server here. LibreChat never sets That matters because of how Airtable's official hosted MCP server (docs) behaves:
The server has a mode that works — and LibreChat can't reach it. So there's no operator-side workaround: not a config change, not a different server setting. The only place this can be fixed is the client. What a user sees:
Everything fails except {"content":[],"structuredContent":{"bases":[...]},"isError":false}Given we opt into PR: #14492 — falls back to serialising Happy to take it a different way if you'd prefer — behind a config flag, or gated on |
|
@danny-avila any thoughts? This actively blocks certain MCPs that follow the standard perfectly fine... Librechat just doesn't follow the standard properly. |
Uh oh!
There was an error while loading. Please reload this page.
What features would you like to see added?
Consider supporting structuredContent as described in the specs: https://modelcontextprotocol.io/specification/2025-06-18/server/tools#structured-content
More details
Which components are impacted by your request?
No response
Pictures
No response
Code of Conduct
All reactions