Skip to content

feat: Expose registry endpoints on feature server for MCP access#6304

Open
patelchaitany wants to merge 1 commit intofeast-dev:masterfrom
patelchaitany:enh/mcp-registry-endpoints-v2
Open

feat: Expose registry endpoints on feature server for MCP access#6304
patelchaitany wants to merge 1 commit intofeast-dev:masterfrom
patelchaitany:enh/mcp-registry-endpoints-v2

Conversation

@patelchaitany
Copy link
Copy Markdown
Contributor

@patelchaitany patelchaitany commented Apr 21, 2026

Summary

  • Mounts the existing REST registry routers (entities, feature views, data sources, feature services, features, lineage, permissions, projects, saved datasets, search) under /registry on the feature server.
  • This enables fastapi_mcp to automatically expose all registry introspection operations as MCP tools when MCP is enabled.
  • Auth is enforced via inject_user_details on every mounted router, consistent with all other feature server endpoints.
  • The RegistryServer is created in-process from store.registry — no external registry server process is required.

Test plan

  • Start feast serve with MCP enabled and verify /registry/entities?project=<proj> returns entity data

  • Verify /registry/feature_views/all lists all feature views across projects

  • Verify auth enforcement: when auth is configured, unauthenticated requests to /registry/* are rejected

  • Confirm MCP tools for registry routes appear when connecting an MCP client to the feature server


Open in Devin Review

@patelchaitany patelchaitany requested a review from a team as a code owner April 21, 2026 12:57
Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 3 additional findings.

Open in Devin Review

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
@patelchaitany patelchaitany force-pushed the enh/mcp-registry-endpoints-v2 branch from d56b8a0 to 9f13194 Compare April 27, 2026 08:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant