💻 feat: Deeper MCP UI integration in the Chat UI #9669

samuelpath · 2025-09-17T13:25:54Z

Note

Most lines of code changed in this PR are tests. Advice for reviewer: first toggle out all test files to focus on the main changes in the logic, since there are not that many of them. And only then can you review the tests.

Summary

The past weeks, we shipped the following 3 PRs to integrate MCP UI with LibreChat:

🎨 feat: MCP UI basic integration #9299
🚦 feat: Simplify MCP UI integration and add unit tests #9418
✂️ refactor: use artifacts and callbacks to pass UI resources #9472 (replaced by this one ✂️ refactor: Artifacts and Tool Callbacks to Pass UI Resources #9581)

These PRs made it such that whenever a tool response would send back a UI Resource, it would be displayed in the tool response detail section, as such:

This was only a first step.

The goal of the current PR is to allow the LLM to integrate UI Resource elements directly as part of the chat response. Here is what we would have now:

Or this:

Or when the chat is able to aggregate UI Resources from multiple tool responses:

You can now interact with UI Resources. When you click on an action for which the client should be aware, a message is posted to the client and can be picked up by the LLM.

For instance here I clicked on "Add to cart" in one of the product cards:

We see that LibreChat gets the message from the UI Resource, interprets it. For now, it's as if the UI Resource is impersonating the user. I will explain below how we intend to improve it in a follow-up PR.

The LLM then calls another tool call that flows from the user action (click on add to cart on a given product, product added to the cart, cart displayed):

Key changes made

1. Plugin-Based Architecture for MCP UI Resources

New Plugin System: Created mcpUIResourcePlugin that processes markdown text and converts UI resource markers (like ui0, ui1,2,3) into proper React components
Inline UI Rendering: UI resources now render directly inline within markdown content instead of being displayed separately

2. Data Structure Improvements

Array Format: Changed UI resources from object format {0: resource, 1: resource} to array format [resource1, resource2] for better indexing and iteration
Simplified Processing: This makes it easier to handle multiple resources and carousel displays

3. New Components Created

MCPUIResource: Renders individual UI resources based on markdown markers and message context
MCPUIResourceCarousel: Handles multiple UI resources in carousel format when multiple indices are specified
Improved UIResourceCarousel: Enhanced with proper action handling using handleUIAction

4. Enhanced Integration Points

Markdown Processing: Integrated the plugin into the main Markdown.tsx component to process UI resource markers
Tool Context: Added helpful context in handleTools.js:346 that instructs AI models how to properly format UI resource markers for inline display
Action Handling: Unified UI action handling through handleUIAction utility that properly submits messages when users interact with UI components

5. Better User Experience

Inline Display: UI resources now appear exactly where the AI places them in the text (e.g., "Here's the product details ui0")
Carousel Support: Multiple resources can be displayed together using comma-separated indices (e.g., ui0,1,2)
Interactive Elements: Users can now interact with UI components and their actions properly trigger new messages

6. Comprehensive Testing

Added extensive test coverage for the new components and plugin functionality
Tests cover edge cases, error handling, and proper integration with message context

The overall improvement transforms MCP UI from a separate attachment display to a seamless, inline experience where AI models can precisely control where and how UI resources appear within their responses.

Samples of improvement follow-ups to come

Have a special persona in the chat flow for messages sent by a UI resource user action to the LLM
Add a user setting to show or hide the messages sent by a UI resource user action to the LLM
Handle hints sent by the MCP server response in the metadata about how to best display the UI Resource

Change Type

Please delete any irrelevant options.

New feature (non-breaking change which adds functionality)
This change requires a documentation update (we'll do the documentation at the end of the iterations)

Testing

Here are the MCP servers I use for my testing:

mcpServers:
  mcp-ui-allbirds-tool-call:
    type: 'streamable-http'
    url: https://mcpstorefront.com/?storedomain=allbirds.com

  mcp-ui-allbirds-intent:
    type: 'streamable-http'
    url: https://mcpstorefront.com/?store=allbirds.com&style=default

  mcp-ui-allbirds-prompt:
    type: 'streamable-http'
    url: https://mcpstorefront.com/?store_domain=allbirds.com

  mcp-aharvard:
    type: 'streamable-http'
    url: https://mcp-aharvard.netlify.app/mcp

For the storefront servers, you can enter a prompt like: "looking for men sneakers", and then try to play with the UI elements displayed.

For the mcp-aharvard server, you can ask what the weather is like in some city.

I've shown above what kind of result you should be seeing.

Test Configuration:

Checklist

Please delete any irrelevant options.

My code adheres to this project's style guidelines
I have performed a self-review of my own code
I have commented in any complex areas of my code
My changes do not introduce new warnings
I have written tests demonstrating that my changes are effective or that my feature works
Local unit tests pass with my changes

danny-avila · 2025-09-17T18:31:02Z

client/src/components/Chat/Messages/Content/ToolCall.tsx


+  // Store UI resources when output is available
+  useEffect(() => {
+    if (output && attachments && !isSubmitting) {


instead of adding this useEffect, can you leverage the existing useAttachments hook?

client/src/hooks/Messages/useAttachments.ts

danny-avila · 2025-09-17T18:38:06Z

packages/api/src/mcp/utils.ts

  }
 }
+
+export const uiResourcesInstructions = `The tool response contains UI resources (i.e. Resource URI starting with "ui://"),


I think it's unnecessary to couple this with artifacts. We can easily show the UI resources adjacent to the tool call, or even in place of the tool call, without needing the LLM to "display" it

it's also possible to create a separate plugin for MCP UI resources if LLM input for rendering is what's desired, similar to the one for web search:
client/src/components/Web/plugin.ts

this would also make it "easier" for the LLM so the "artifacts" boilerplate is not necessary. In my experience, it's best to reduce the amount the LLM has to generate and even key the specific "attachment" to render, so it doesn't need to generate a long string to render the expected output.

For example, in web search, we can reference specific links from the search like this:
\ueturn0search3

api/app/clients/tools/util/handleTools.js

danny-avila · 2025-09-24T10:38:56Z

client/src/components/MCPUIResource/plugin.ts

+import type { Node } from 'unist';
+import type { UIResourceNode } from './types';
+
+export const UI_RESOURCE_MARKER = '\ue205';


I would not recommend using this as a marker, and instead use \ui or something similar, especially since the marker does not vary from \ue205.

As long as the plugin correctly falls back to \ui or the chosen marker, if it has no corresponding resource, to avoid edge cases where the AI writes the marker for purposes not related to UI resources.

Using "unicode-like" markers was a convention introduced by ChatGPT for their web search, which was a large inspiration for LC's UI/LLM interaction

Done! The marker is now \ui0 (or any other index) to show the resources. It works just as well!

danny-avila · 2025-09-25T12:31:36Z

api/app/clients/tools/util/handleTools.js

      };
      continue;
    } else if (tool && mcpToolPattern.test(tool)) {
+      toolContextMap[tool] = `# MCP Tool \`${tool}\`:


I take issue with this being added to all MCP tools. These instructions can be part of the response that we format in formatToolContent i.e. packages/api/src/mcp/parsers.ts to ensure it's only applied once per "MCP UI" output.

Even better, would be to make use of serverInstructions for this to be on the MCP server to provide:
https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/mcp_servers#serverinstructions

Some MCP Servers have 50+ tools and are loaded individually at this level, and we would have repeated instructions for them all.

I agree that we don't need to add this to all MCP tools and I think formatToolContent is the right place for this.

These instructions aren't about how to use the tools on the server, but rather what to do with the tool response, i.e. how to render them in the client using markers. This is specific to LibreChat's implementation of MCP-UI, and other MCP clients could choose to use a different marker or syntax to render UI resources. This makes no difference for the MCP server, so I don't think the serverInstructions are the right place. What do you think?

danny-avila · 2025-09-25T12:38:25Z

client/src/components/Chat/Messages/Content/UIResourceCarousel.tsx

  const [showRightArrow, setShowRightArrow] = useState(true);
  const [isContainerHovered, setIsContainerHovered] = useState(false);
  const scrollContainerRef = React.useRef<HTMLDivElement>(null);
+  const { submitMessage } = useSubmitMessage();


We should not utilize this hook within the message tree as it can cause unnecessary re-renders across all messages and cause significant client latency.

See ~/components/Chat/Messages/Content/Parts/EditTextPart and client/src/components/Chat/Messages/Content/EditMessage.tsx for how this is prevented and submissions are still allowed.

client/src/components/Chat/Messages/Content/Markdown.tsx

danny-avila · 2025-09-25T12:40:28Z

client/src/components/MCPUIResource/MCPUIResource.tsx

+  const localize = useLocalize();
+  const { submitMessage } = useSubmitMessage();
+  const { messageId } = useMessageContext();
+  const { conversation } = useChatContext();


useChatContext and useSubmitMessage should not be used here as they can cause unnecessary re-renders across all messages and cause significant client latency.

See how other adjacent components access the same things (EditTextPart and EditMessage for submissions)

danny-avila · 2025-09-25T12:40:45Z

client/src/components/MCPUIResource/MCPUIResourceCarousel.tsx

+
+export function MCPUIResourceCarousel(props: MCPUIResourceCarouselProps) {
+  const { messageId } = useMessageContext();
+  const { conversation } = useChatContext();


No use of useChatContext allowed here (will cause lag within the message tree)

danny-avila · 2025-09-25T12:44:07Z

I was able to resolve significant client rendering delays in this PR by addressing similar concerns based on my latest review:

https://github.com/danny-avila/LibreChat/pull/9678/files

SebastianAwaze · 2025-10-07T14:02:42Z

Excited for this to get in!

mhempstock · 2025-10-13T14:09:51Z

Looking forward to this, saw the great presentation at the MCP London conference, which pushed me to add an MCP-UI to one of our current servers. Found it a little limited when it comes to UX right now. Once this is in place, it will enable make so many things possible!

plgodin · 2025-10-16T19:07:25Z

Just addressed your comments by refactoring to a better approach that makes UI Resources available throughout the conversation, and also works when sharing conversations! Give this a spin and let me know what you think!

plgodin · 2025-10-16T19:09:03Z

Looks like I can't mark this PR as ready for review... @danny-avila would you mind giving me the required permissions?

Anthony-Jhoiro · 2025-10-22T09:21:36Z

Hello!
I tried this PR locally, globally it works fine. But I couldn't make it work using the initial render data even with the MCP-UI documentation code.
Has anyone tried to use initial render data successfully with librechat ? I am new with mcp-ui, I might have missed something.
To reproduce:

checkout the PR and run librechat
create an mcp ui that will return an url like this:

  return createUIResource({
    uri: uiUri as `ui://${string}`,
    content: {
      type: 'externalUrl',
      iframeUrl: `${baseUrl}${route}?waitForRenderData=true`,
    },
    encoding: 'text',
    uiMetadata: {
      'initial-render-data': props,
    },
  });

listen for events and submit

    window.addEventListener('message', (event) => {
      if (event.data.type ==='ui-lifecycle-iframe-render-data') {
        console.log('mount the app')
      }  });
    window.parent.postMessage({ type: 'ui-request-render-data', messageId }, '*');

the component is never mounted (the console.log does not trigger)
Thanks

samuelpath · 2025-10-27T17:04:45Z

@Anthony-Jhoiro Thanks for your feedback. We haven't yet considered this use case. We'll do it in the next iteration, after this current PR is reviewed and merged by @danny-avila. Thanks for your patience!

samuelpath · 2025-11-18T14:12:54Z

@danny-avila do you think you may have time for this 2-months old PR this week? I know you must be very busy…!

@plgodin do you think you can resolve the new merge conflicts to facilitate @danny-avila's final review here?

danny-avila · 2025-11-18T16:37:01Z

Sorry for the wait on this. Would like to merge asap, and updating the branch will help!

plgodin · 2025-11-26T23:45:25Z

I just rebased and updated the branch! @danny-avila we should be good for a final review and merge!

Copilot

Pull request overview

This PR implements deeper MCP UI integration by enabling inline rendering of UI resources directly within chat messages, rather than only in tool response detail sections. The AI can now precisely control where UI elements appear in responses using special markers.

Key Changes:

Introduced a plugin-based architecture that transforms UI resource markers (e.g., \ui{abc123}) into React components during markdown rendering
Changed UI resources from object format to array format for better iteration and carousel support
Added cross-conversation resource resolution via stable resource IDs generated from content hashes
Enhanced Share view to support MCP UI resources through a new ShareMessagesProvider

Reviewed changes

Copilot reviewed 26 out of 27 changed files in this pull request and generated 10 comments.

Show a summary per file

File	Description
`packages/data-provider/src/schemas.ts`	Updated `UIResource` type to require `resourceId` and `uri` fields, removing optional `type` and `data` fields
`packages/api/src/mcp/utils.ts`	Fixed trailing whitespace in comment
`packages/api/src/mcp/types/index.ts`	Simplified `FormattedContent` type by removing metadata field from text content
`packages/api/src/mcp/parsers.ts`	Added resource ID generation, UI marker hints in tool responses, and instructions for LLM on how to use markers
`packages/api/src/mcp/__tests__/parsers.test.ts`	Updated tests to verify resource ID generation and UI marker formatting
`client/src/utils/index.ts`	Added `handleUIAction` utility to process user interactions with UI resources and submit messages to the LLM
`client/src/store/misc.ts`	Added `conversationAttachmentsSelector` to filter attachments by conversation for efficient resource lookup
`client/src/locales/en/translation.json`	Added error message translations for UI resource not found and rendering errors
`client/src/hooks/useResourcePermissions.ts`	Added default export for consistency with other hooks
`client/src/hooks/index.ts`	Changed import to use default export for `useResourcePermissions`
`client/src/hooks/Messages/useConversationUIResources.ts`	New hook that collects all UI resources in a conversation indexed by resource ID for cross-turn references
`client/src/components/Share/ShareView.tsx`	Wrapped `MessagesView` with `ShareMessagesProvider` to enable UI resources in shared conversations
`client/src/components/Share/ShareMessagesProvider.tsx`	New provider that supplies message context for share view, enabling existing hooks to work in read-only mode
`client/src/components/MCPUIResource/types.ts`	Defined TypeScript types for UI resource AST nodes used by the markdown plugin
`client/src/components/MCPUIResource/plugin.ts`	Implemented remark plugin that parses `\ui{id}` markers and transforms them into React component nodes
`client/src/components/MCPUIResource/index.ts`	Barrel export for MCP UI Resource components and utilities
`client/src/components/MCPUIResource/__tests__/plugin.test.ts`	Comprehensive tests for marker parsing, including single resources, carousels, and edge cases
`client/src/components/MCPUIResource/__tests__/MCPUIResourceCarousel.test.tsx`	Tests for carousel rendering with multiple resources and error handling
`client/src/components/MCPUIResource/__tests__/MCPUIResource.test.tsx`	Tests for single resource rendering, cross-conversation lookup, and error states
`client/src/components/MCPUIResource/MCPUIResourceCarousel.tsx`	Component that renders multiple UI resources in a carousel format
`client/src/components/MCPUIResource/MCPUIResource.tsx`	Component that renders individual UI resources inline with error handling
`client/src/components/Chat/Messages/Content/__tests__/UIResourceCarousel.test.tsx`	Updated tests to use `handleUIAction` instead of console logging
`client/src/components/Chat/Messages/Content/__tests__/Markdown.mcpui.test.tsx`	New integration test verifying UI resources render correctly within markdown
`client/src/components/Chat/Messages/Content/UIResourceCarousel.tsx`	Updated to use `handleUIAction` for consistent action handling across carousel and inline resources
`client/src/components/Chat/Messages/Content/Markdown.tsx`	Integrated `mcpUIResourcePlugin` and registered MCP UI components for markdown rendering
`client/src/Providers/MessagesViewContext.tsx`	Exported context and type to allow `ShareMessagesProvider` to implement the same interface
`api/server/controllers/agents/__tests__/callbacks.spec.js`	Updated tests to use array format for UI resources instead of object format with numeric keys

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.

client/src/utils/index.ts

packages/api/src/mcp/parsers.ts

client/src/store/misc.ts

client/src/components/MCPUIResource/MCPUIResource.tsx

Copilot · 2025-12-01T23:06:47Z

client/src/components/MCPUIResource/MCPUIResource.tsx

+          onUIAction={async (result) => handleUIAction(result, ask)}
+          htmlProps={{
+            autoResizeIframe: { width: true, height: true },
+            sandboxPermissions: 'allow-popups allow-popups-to-escape-sandbox',


Potential security concern: The sandboxPermissions value 'allow-popups allow-popups-to-escape-sandbox' allows content to escape the iframe sandbox, which could pose security risks when rendering untrusted UI resources from external MCP servers.

Consider whether these permissions are necessary for the use case. If popups must be allowed, document why this is safe in this context, or consider adding user warnings/confirmations for untrusted sources.

Suggested change

sandboxPermissions: 'allow-popups allow-popups-to-escape-sandbox',

// Only 'allow-popups' is permitted; 'allow-popups-to-escape-sandbox' is removed for security.

sandboxPermissions: 'allow-popups',

client/src/utils/index.ts

packages/api/src/mcp/parsers.ts

client/src/components/Share/ShareView.tsx

client/src/components/MCPUIResource/plugin.ts

dustinhealy

@samuelpath @plgodin

Hi all,

I've just finished my review and everything looks good to me. Once the recent Copilot comments have been addressed I will approve the changes and hand it off to Danny for a final sign off prior to merge.

The only friction I ran into during this review was related to AI responses incorrectly presenting the UI markers (erroneously wrapping markers in LaTex delimiters leading them to be converted into math nodes before they can be handled by the mcpUIResourcePlugin, responding with individual UIResources that are meant to be rendered within a UIResourceCarousel, etc.) causing them not to be rendered properly, but that is due to the relative strength of the models I was testing with and the context provided by the tool call responses from the MCP servers, not the implementation of the mcp-ui integration itself.

My main note which can likely be handled in a future PR is that in a shared conversation, currently there is no feedback mechanism for when a user performs a UIAction on an interactable UIResource. Of course, the core of this behavior is expected since the current strategy for handleUIAction is to send a message within the conversation / call a tool, and shared conversations in their present state are read-only; thus, such a solution is not viable. However, there still should be some indication to the user that interactions will not work as intended within that shared view beyond the console logs currently occurring when something like an "Add to Cart" button is pressed. Perhaps triggering a explanatory toast within handleUIAction for this scenario would be sufficient.

Thank you for your work on this PR - very excited to get this merged in. I believe this is a feature that many users will benefit from.

dustinhealy · 2025-12-10T21:51:37Z

Update:

Moving this PR to a new branch so that commits to address the GitHub Copilot comments can be pushed up (currently unable to because I lack permissions on the originating fork / the option to allow collaborators to push commits for this PR is not enabled)

@samuelpath @plgodin I would appreciate if you could look over my changes in the new PR when you have a moment prior to this being merged where I attempted to address the Copilot comments and make sure everything looks right to you and if you could share what you think of the validity of the final unresolved Copilot comment and whether you think it requires further review / changes.

Potential security concern: The sandboxPermissions value 'allow-popups allow-popups-to-escape-sandbox' allows content to escape the iframe sandbox, which could pose security risks when rendering untrusted UI resources from external MCP servers.

Consider whether these permissions are necessary for the use case. If popups must be allowed, document why this is safe in this context, or consider adding user warnings/confirmations for untrusted sources.

--------- Co-authored-by: Samuel Path <[email protected]> Co-authored-by: Pierre-Luc Godin <[email protected]>

…erencing - Replace index-based resource markers with stable resource IDs - Update plugin to parse \ui{resourceId} format instead of \ui0 - Refactor components to use useMessagesOperations instead of useSubmitMessage - Add ShareMessagesProvider for UI resources in share view - Add useConversationUIResources hook for cross-turn resource lookups - Update parsers to generate resource IDs from content hashes - Update all tests to use resource IDs instead of indices - Add sandbox permissions for iframe popups - Remove deprecated MCP tool context instructions

plgodin · 2025-12-11T19:17:01Z

@danny-avila @dustinhealy I removed the extra permission from the MCPUIResource iframe, as Copilot's concern is valid and there are ways to securely open new pages from within a tool without opening this permission. I also fixed the merge conflicts. We should be ready to go! cc. @samuelpath

danny-avila · 2025-12-11T21:02:19Z

Thanks for all your hard work and patience on this! I'm just going to approve while I clean up the dev-staging branch so another rebase is not necessary.

We will check for what @dustinhealy if it's included and if not, we will open a new PR
#10898

* 💻 feat: deeper MCP UI integration in the chat UI using plugins --------- Co-authored-by: Samuel Path <[email protected]> Co-authored-by: Pierre-Luc Godin <[email protected]> * 💻 refactor: Migrate MCP UI resources from index-based to ID-based referencing - Replace index-based resource markers with stable resource IDs - Update plugin to parse \ui{resourceId} format instead of \ui0 - Refactor components to use useMessagesOperations instead of useSubmitMessage - Add ShareMessagesProvider for UI resources in share view - Add useConversationUIResources hook for cross-turn resource lookups - Update parsers to generate resource IDs from content hashes - Update all tests to use resource IDs instead of indices - Add sandbox permissions for iframe popups - Remove deprecated MCP tool context instructions --------- Co-authored-by: Pierre-Luc Godin <[email protected]>

liady · 2025-12-23T06:53:26Z

Really great to see this merged! Really awesome work @samuelpath , @plgodin ,@dustinhealy and the team 👏
Note that the official MCP Apps spec is soon to be approved, and very soon MCP-UI client SDK will support it seamlessly.
Let us know if we can help in any way.

idosal · 2025-12-23T07:56:14Z

This is incredible @samuelpath ,@dustinhealy, @plgodin! Thanks for making this happen. It's amazing to see a great project like LibreChat expand its MCP-UI support.

As Liad mentioned, the new MCP Apps client will be released soon. You can already play with it in the mcp-ui/client alpha.

* 💻 feat: deeper MCP UI integration in the chat UI using plugins --------- Co-authored-by: Samuel Path <[email protected]> Co-authored-by: Pierre-Luc Godin <[email protected]> * 💻 refactor: Migrate MCP UI resources from index-based to ID-based referencing - Replace index-based resource markers with stable resource IDs - Update plugin to parse \ui{resourceId} format instead of \ui0 - Refactor components to use useMessagesOperations instead of useSubmitMessage - Add ShareMessagesProvider for UI resources in share view - Add useConversationUIResources hook for cross-turn resource lookups - Update parsers to generate resource IDs from content hashes - Update all tests to use resource IDs instead of indices - Add sandbox permissions for iframe popups - Remove deprecated MCP tool context instructions --------- Co-authored-by: Pierre-Luc Godin <[email protected]>

samuelpath force-pushed the mcp-ui-next branch from 9933de0 to 2fc4441 Compare September 17, 2025 18:11

samuelpath marked this pull request as ready for review September 17, 2025 18:18

danny-avila requested changes Sep 17, 2025

View reviewed changes

danny-avila marked this pull request as draft September 18, 2025 12:47

samuelpath force-pushed the mcp-ui-next branch from 2fc4441 to 9d8cb66 Compare September 23, 2025 08:00

github-advanced-security bot found potential problems Sep 23, 2025

View reviewed changes

api/app/clients/tools/util/handleTools.js Fixed Show fixed Hide fixed

samuelpath force-pushed the mcp-ui-next branch 2 times, most recently from 9225fbd to 2d7b88e Compare September 23, 2025 13:38

samuelpath marked this pull request as ready for review September 23, 2025 13:38

samuelpath force-pushed the mcp-ui-next branch from 2d7b88e to e21eab2 Compare September 23, 2025 13:42

danny-avila requested changes Sep 24, 2025

View reviewed changes

plgodin force-pushed the mcp-ui-next branch from e21eab2 to fcf97ac Compare September 24, 2025 19:44

samuelpath force-pushed the mcp-ui-next branch from fcf97ac to 42ee75f Compare September 25, 2025 09:25

danny-avila requested changes Sep 25, 2025

View reviewed changes

danny-avila marked this pull request as draft September 25, 2025 12:44

plgodin force-pushed the mcp-ui-next branch 2 times, most recently from 0d185fd to 50aa85a Compare October 16, 2025 18:51

samuelpath marked this pull request as ready for review October 17, 2025 08:19

samuelpath force-pushed the mcp-ui-next branch from 50aa85a to 4382fa3 Compare October 17, 2025 08:23

plgodin force-pushed the mcp-ui-next branch from 4382fa3 to ae89b95 Compare October 17, 2025 15:00

samuelpath force-pushed the mcp-ui-next branch from ae89b95 to b25c657 Compare October 19, 2025 16:01

samuelpath requested a review from danny-avila October 19, 2025 19:56

danny-avila changed the base branch from main to dev November 4, 2025 18:43

plgodin force-pushed the mcp-ui-next branch from b25c657 to d3a8936 Compare November 26, 2025 23:19

danny-avila requested a review from Copilot December 1, 2025 23:01

Copilot started reviewing on behalf of danny-avila December 1, 2025 23:02 View session

Copilot finished reviewing on behalf of danny-avila December 1, 2025 23:05

Copilot AI reviewed Dec 1, 2025

View reviewed changes

danny-avila requested a review from dustinhealy December 3, 2025 19:37

dustinhealy reviewed Dec 4, 2025

View reviewed changes

dustinhealy changed the base branch from dev to dev-staging December 4, 2025 17:28

danny-avila force-pushed the dev-staging branch from 8a35d16 to 6aa696b Compare December 4, 2025 19:35

dustinhealy mentioned this pull request Dec 10, 2025

💻 feat: deeper MCP UI integration in the chat UI #10898

Closed

8 tasks

💻 feat: deeper MCP UI integration in the chat UI using plugins

79c7cb8

--------- Co-authored-by: Samuel Path <[email protected]> Co-authored-by: Pierre-Luc Godin <[email protected]>

plgodin force-pushed the mcp-ui-next branch 2 times, most recently from 8e1cfbd to 1e24fbf Compare December 10, 2025 22:12

plgodin force-pushed the mcp-ui-next branch from 1e24fbf to 3aa569d Compare December 11, 2025 19:11

danny-avila approved these changes Dec 11, 2025

View reviewed changes

danny-avila changed the title ~~💻 feat: deeper MCP UI integration in the chat UI~~ 💻 feat: Deeper MCP UI integration in the Chat UI Dec 11, 2025

danny-avila merged commit 70012f5 into danny-avila:dev-staging Dec 11, 2025
7 checks passed

dustinhealy mentioned this pull request Dec 12, 2025

👨‍✈️ chore: Minor MCP-UI Logic Cleanup #10950

Merged

6 tasks

	sandboxPermissions: 'allow-popups allow-popups-to-escape-sandbox',
	// Only 'allow-popups' is permitted; 'allow-popups-to-escape-sandbox' is removed for security.
	sandboxPermissions: 'allow-popups',

Uh oh!

💻 feat: Deeper MCP UI integration in the Chat UI #9669

💻 feat: Deeper MCP UI integration in the Chat UI #9669

Uh oh!

Conversation

samuelpath commented Sep 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Key changes made

Samples of improvement follow-ups to come

Change Type

Testing

Test Configuration:

Checklist

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

danny-avila Sep 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

danny-avila commented Sep 25, 2025

Uh oh!

SebastianAwaze commented Oct 7, 2025

Uh oh!

mhempstock commented Oct 13, 2025

Uh oh!

plgodin commented Oct 16, 2025

Uh oh!

plgodin commented Oct 16, 2025

Uh oh!

Anthony-Jhoiro commented Oct 22, 2025

Uh oh!

samuelpath commented Oct 27, 2025

Uh oh!

samuelpath commented Nov 18, 2025

Uh oh!

danny-avila commented Nov 18, 2025

Uh oh!

plgodin commented Nov 26, 2025

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI Dec 1, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

dustinhealy left a comment

Choose a reason for hiding this comment

Uh oh!

dustinhealy commented Dec 10, 2025

samuelpath commented Sep 17, 2025 •

edited

Loading

danny-avila Sep 25, 2025 •

edited

Loading

danny-avila commented Dec 11, 2025 •

edited

Loading

liady commented Dec 23, 2025 •

edited

Loading