Feast MCP Server

Standalone MCP server for Feast, built on the MCP SDK.

Currently operates as a proxy — it forwards every tool call to an upstream Feast feature server over HTTP, passing through the caller's Authorization: Bearer <token> header so that the feature server handles OIDC / Kubernetes RBAC as usual.

Quick start

cd MCP
pip install -e .

# stdio (default) — point at your running Feast feature server
feast-mcp --feast-url http://localhost:6566

# SSE transport on a custom port
feast-mcp --feast-url http://localhost:6566 --transport sse --port 8000

Related MCP server: MCP Manager

Tools exposed

Authorization

The MCP server itself does not validate tokens. It forwards the bearer token from the MCP request context to the upstream feature server, which performs OIDC or Kubernetes token validation and RBAC enforcement.

IDE / client configuration

{
  "mcpServers": {
    "feast": {
      "command": "feast-mcp",
      "args": ["--feast-url", "http://localhost:6566"]
    }
  }
}