You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/getting-started/genai.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -146,10 +146,13 @@ Feast supports the Model Context Protocol (MCP), which enables AI agents and app
146
146
type: mcp
147
147
enabled: true
148
148
mcp_enabled: true
149
+
mcp_transport: http
149
150
mcp_server_name: "feast-feature-store"
150
151
mcp_server_version: "1.0.0"
151
152
```
152
153
154
+
By default, Feast uses the SSE-based MCP transport (`mcp_transport: sse`). Streamable HTTP (`mcp_transport: http`) is recommended for improved compatibility with some MCP clients.
155
+
153
156
### How It Works
154
157
155
158
The MCP integration uses the `fastapi_mcp` library to automatically transform your Feast feature server's FastAPI endpoints into MCP-compatible tools. When you enable MCP support:
Feast can expose the Python Feature Server as an MCP (Model Context Protocol) server using `fastapi_mcp`. When enabled, MCP clients can discover and call Feast tools such as online feature retrieval.
6
+
7
+
## Installation
8
+
9
+
```bash
10
+
pip install feast[mcp]
11
+
```
12
+
13
+
## Configuration
14
+
15
+
Add an MCP `feature_server` block to your `feature_store.yaml`:
16
+
17
+
```yaml
18
+
feature_server:
19
+
type: mcp
20
+
enabled: true
21
+
mcp_enabled: true
22
+
mcp_transport: http
23
+
mcp_server_name: "feast-feature-store"
24
+
mcp_server_version: "1.0.0"
25
+
```
26
+
27
+
### mcp_transport
28
+
29
+
`mcp_transport` controls how MCP is mounted into the Feature Server:
30
+
31
+
- `sse`: SSE-based transport. This is the default for backward compatibility.
32
+
- `http`: Streamable HTTP transport. This is recommended for improved compatibility with some MCP clients.
33
+
34
+
If `mcp_transport: http` is configured but your installed `fastapi_mcp` version does not support Streamable HTTP mounting, Feast will fail fast with an error asking you to upgrade `fastapi_mcp` (or reinstall `feast[mcp]`).
35
+
36
+
## Endpoints
37
+
38
+
MCP is mounted at:
39
+
40
+
- `/mcp`
41
+
42
+
## Connecting an MCP client
43
+
44
+
Use your MCP client’s “HTTP” configuration and point it to the Feature Server base URL. For example, if your Feature Server runs at `http://localhost:6566`, use:
45
+
46
+
- `http://localhost:6566/mcp`
47
+
48
+
## Troubleshooting
49
+
50
+
- If you see a deprecation warning about `mount()` at runtime, upgrade `fastapi_mcp` and use `mcp_transport: http` or `mcp_transport: sse`.
51
+
- If your MCP client has intermittent connectivity issues with `mcp_transport: sse`, switch to `mcp_transport: http`.
0 commit comments