Repository navigation
Add remote MCP with browser OAuth - #12
Open
bluebird42 wants to merge 1 commit into
Open
bluebird42 wants to merge 1 commit into
bluebird42 wants to merge 1 commit into
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.
What changes
Adds a hosted remote MCP endpoint to Core at
/mcp, intended forhttps://api.mave.io/mcp. Clients can connect through the existing Mave sign-in flow, choose a space, and approve read-only or explicitly requested write access. The consent screen reuses the CLI authentication card; Connected apps lets users revoke access immediately.mave-cli, using Core's existing tenant-scoped contexts. Destructive calls require explicit confirmation arguments.Rollout
Deploy through the normal Core release and migration process. The migration adds three MCP tables. Set
MAVE_MCP_RESOURCE_URL=https://api.mave.io/mcpand route the API discovery/OAuth paths documented indocs/mcp.md; the dashboard serves authorization and connection management. No separate MCP service is required. This PR does not deploy the endpoint.The transport supports MCP 2025 Streamable HTTP with JSON responses; it does not advertise SSE subscriptions or the 2026 envelope protocol. Local file uploads and Vimeo migration remain CLI operations.
Validation
mix credo --strict,mix precommit,mix security.enforce, JavaScript syntax checks and npm audit passed.