GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Enable MCP support for Feast · Issue #5404 · feast-dev/feast

Enable MCP support for Feast #5404

New issue
Copy link
New issue
Copy link
Closed
#5406
Closed
Enable MCP support for Feast#5404
#5406
Copy link
Labels
kind/featureNew feature or requestNew feature or request

Description

@franciscojavierarceo
franciscojavierarceo
opened on May 30, 2025
Issue body actions

Is your feature request related to a problem? Please describe.
Feast uses FastAPI for its feature server.

We can use https://github.com/tadata-org/fastapi_mcp to expose Feast as an MCP Server.

Describe the solution you'd like
This should be optional based on the feature store yaml and default to false.

Describe alternatives you've considered
N/A

Additional context
Add any other context or screenshots about the feature request here.

Reacted by Nikhil Kathole

Activity

  1. franciscojavierarceo
    added
    kind/featureNew feature or requestNew feature or request
    on May 30, 2025
  2. YassinNouh21 commented on May 31, 2025

    @YassinNouh21
    YassinNouh21
    on May 31, 2025
    Collaborator
    More actions

    Hi @franciscojavierarceo ! I'd like to implement MCP support for Feast as requested. Here's my proposed approach:

    Implementation Overview:

    • Add optional MCP server support using fastapi_mcp library
    • Configuration-driven via feature_store.yaml with mcp_enabled: false as default
    • Non-breaking changes with graceful degradation when fastapi_mcp is not installed

    MCP Tools Exposed:

    • get_online_features - retrieve features for entities
    • list_feature_views - enumerate available feature views
    • list_feature_services - enumerate available feature services
    • get_feature_store_info - basic store metadata

    Configuration Example:

    feature_server:
      type: mcp
      mcp_enabled: true  # defaults to false
      mcp_server_name: "feast-mcp-server"
      mcp_server_version: "1.0.0"

    This follows Feast's existing patterns for feature server configuration and maintains full backward compatibility. Would you like me to proceed with creating a PR?

    Reacted by Francisco Javier Arceo
  3. franciscojavierarceo commented on May 31, 2025

    @franciscojavierarceo
    franciscojavierarceo
    on May 31, 2025
    MemberAuthor
    More actions

    That'd be awesome!

  4. YassinNouh21 commented on May 31, 2025

    @YassinNouh21
    YassinNouh21
    on May 31, 2025
    Collaborator
    More actions

    PR is ready can u take a look @franciscojavierarceo

  5. redhatHameed commented on May 31, 2025

    @redhatHameed
    redhatHameed
    on May 31, 2025
    Contributor
    More actions

    @franciscojavierarceo @YassinNouh21

    Feast has three remote server configurations (online, offline, and registry), each with its own implementation. The question is: what functions does the MCP server expose? will be different server for each implementation or single server or just implementing online feature server ?

    Im not very familiar with the MCP server yet and haven't looked at the PR, so please ignore the question is not relevant

  6. franciscojavierarceo commented on May 31, 2025

    @franciscojavierarceo
    franciscojavierarceo
    on May 31, 2025
    MemberAuthor
    More actions

    Good question @redhatHameed! I should have been more explicit to limit it to the online feature server, though some of that does allow for retrieval of data from the offline store.

  7. YassinNouh21 commented on May 31, 2025

    @YassinNouh21
    YassinNouh21
    on May 31, 2025
    Collaborator
    More actions

    @redhatHameed
    "Will it be different servers or single server or just online feature server?"
    Single server: MCP enhances the online feature server only
    Not separate servers: It's the same FastAPI application with MCP capabilities added
    Online-focused: Currently only applies to online feature serving, not offline or registry operations
    So MCP gives you all the standard online feature server functionality PLUS the ability for AI agents to interact with it through the Model Context Protocol.

  8. franciscojavierarceo
    closed this as completedin #5406on Jun 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureNew feature or requestNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.