WIP: app: Add MCP server support for ai-assistant

[ashu8912]

Adds support for running MCP (Model Context Protocol) servers from the desktop app by integrating @langchain/mcp-adapters library and creating a client architecture to manage MCP server connections.

• Integrates MCP server management capabilities into the Electron desktop application
• Provides IPC APIs for tool discovery, execution, and configuration management
• Implements proper cleanup and initialization patterns for MCP client lifecycle

Screenshots

How to test

[joaquimrocha]

The app laywer always has to double check for potentially destructive actions or portentially disruptive ones, like setting up MCP servers.

[Copilot]

Pull Request Overview

Adds support for running MCP (Model Context Protocol) servers from the desktop app by integrating @langchain/mcp-adapters library and creating a client architecture to manage MCP server connections.

• Integrates MCP server management capabilities into the Electron desktop application
• Provides IPC APIs for tool discovery, execution, and configuration management
• Implements proper cleanup and initialization patterns for MCP client lifecycle

Reviewed Changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 1 comment.

File	Description
app/package.json	Adds @langchain/mcp-adapters dependency and includes mcp-client.js in build files
app/electron/preload.ts	Exposes MCP client APIs to renderer process via IPC bridge
app/electron/mcp-client.ts	Implements complete MCP client with server management, tool execution, and configuration handling
app/electron/main.ts	Integrates MCP client into main Electron process with proper lifecycle management

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[illume]

Very cool.

Could you please add a PR description?

Threat modeling with mitigations should be done. Some things to consider: IPC auth, env var leakage, logging of sensitive info, limits on tool execution, looking at if config can be used to execute, parsing/validation of inputs/outputs, sandboxing, UX view of what tools are doing and if tools are on.

Is this worth doing this backend now instead so we don't have to finish and maintain two versions of this code?

[Copilot]

Pull Request Overview

Copilot reviewed 5 out of 6 changed files in this pull request and generated 2 comments.

Comments suppressed due to low confidence (2)

app/electron/mcp-client.ts:1

• Debug console.log statement should be removed or replaced with proper logging. This appears to be leftover debug code that clutters the production output.

/*

app/electron/mcp-client.ts:1

• Multiple debug console.log statements throughout initializeToolsConfig (lines 206, 215, 223, 232, 244, 247) should be removed or replaced with a proper logging framework for production code.

/*

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[k8s-ci-robot]

Keywords which can automatically close issues and at(@) or hashtag(#) mentions are not allowed in commit messages.

The list of commits with invalid commit messages:

• 7db4e55 build(deps): bump playwright and @playwright/test in /e2e-tests
• 7405705 build(deps): bump playwright and @playwright/test in /app/e2e-tests

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[illume]

Going to continue this here:
#4135