-
Notifications
You must be signed in to change notification settings - Fork 444
Add support for running mcp servers from desktop app #3888
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ashu8912 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
07f292f
to
99b2593
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The app laywer always has to double check for potentially destructive actions or portentially disruptive ones, like setting up MCP servers.
}); | ||
|
||
// Handle MCP tool execution | ||
ipcMain.handle('mcp-execute-tool', async (event, { toolName, args, toolCallId }) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to check if the tool is enabled. The source of truth for this needs to be on the app layer side, and the user needs to confirm it the first time it's configured.
}); | ||
|
||
// Handle MCP configuration updates | ||
ipcMain.handle('mcp-update-config', async (event, mcpConfig: MCPConfig) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We also need to confirm with the user that the configuration is what's desired, unless we're just disabling an MCP server.
No description provided.