feat: Expose registry endpoints on feature server for MCP access#6304
Open
patelchaitany wants to merge 1 commit intofeast-dev:masterfrom
Open
feat: Expose registry endpoints on feature server for MCP access#6304patelchaitany wants to merge 1 commit intofeast-dev:masterfrom
patelchaitany wants to merge 1 commit intofeast-dev:masterfrom
Conversation
Mount the existing REST registry routers under /registry on the feature server so that fastapi_mcp automatically exposes registry introspection (list/get for entities, feature views, data sources, feature services, permissions, projects, saved datasets, lineage, search) as MCP tools. The RegistryServer is created in-process from store.registry — no external registry server is required. Auth is enforced via inject_user_details on every mounted router. Made-with: Cursor Signed-off-by: Chaitany patel <patelchaitany93@gmail.com> Made-with: Cursor
d56b8a0 to
9f13194
Compare
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
/registryon the feature server.fastapi_mcpto automatically expose all registry introspection operations as MCP tools when MCP is enabled.inject_user_detailson every mounted router, consistent with all other feature server endpoints.RegistryServeris created in-process fromstore.registry— no external registry server process is required.Test plan
Start
feast servewith MCP enabled and verify/registry/entities?project=<proj>returns entity dataVerify
/registry/feature_views/alllists all feature views across projectsVerify auth enforcement: when auth is configured, unauthenticated requests to
/registry/*are rejectedConfirm MCP tools for registry routes appear when connecting an MCP client to the feature server