feat: add Connector Gateway UI and MCP wiring#1776
Open
4pmtong wants to merge 3 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related Issue
Closes #
Description
Adds the first Eigent-side Connector Gateway integration.
Introduce a generic Connector Gateway UI and wiring for hosted connector runtimes, while keeping the frontend/backend naming provider-agnostic so we are not tightly coupled to OpenConnector long term.
Changes include:
Testing Evidence (REQUIRED)
Testing performed:
What is the purpose of this pull request?
Contribution Guidelines Acknowledgement
Notes for Reviewers
This PR depends on the companion eigent_server Connector Gateway deployment/configuration. The desktop app should not talk to OpenConnector directly; it only consumes eigent_server connector APIs and MCP config.