feat: add hosted MCP connectors and OAuth compatibility - #235
Merged
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.
Summary
mcp_oauthkind.Why
Earlier MCP Directory builds could leave Notion, Linear, or Sentry data using provider-specific OAuth kinds. Some databases also reached migration versions 11 or 12 on those builds, which means Goose will skip the current main branch migration 000010. Migration 000013 registers the generic kind idempotently and preserves those existing credentials and bindings.
Architecture
This reuses the existing MCP Catalog, Capability, Capability Version, Secret, and Agent Capability structures. It does not add tables, APIs, Store methods, Runtime paths, or frontend permission changes.
Validation
make checkmake check-storego test ./server/internal/mcpcatalog./scripts/verify-migration-order.sh origin/mainScope
Miro is intentionally excluded until its OAuth and conversation flow are verified end to end.