Skip to content

docs(mcp): the minimum mcp is 1.22 (forge-cli #710) #148

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
fas89 merged 1 commit into from
Oct 11, 2026
Merged

docs(mcp): the minimum mcp is 1.22 (forge-cli #710) #148

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/cli/mcp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,9 +81,9 @@ Both servers run on the official `mcp` Python SDK.

| | |
| --- | --- |
| **Dependency pin** | `mcp>=1.20,<3.0` |
| **Dependency pin** | `mcp>=1.22,<3.0` *(unreleased, [forge-cli #710](https://github.com/Agenticstiger/forge-cli/pull/710); 0.19.0 and earlier pin `mcp>=1.20,<3.0`)* |
| **What a fresh install resolves** | The newest `2.x`. `mcp` is a core dependency rather than an extra, so `pip install data-product-forge` picks it up. A fresh 0.18.1 install resolved `mcp 2.3.0` on 5 Oct 2026. |
| **Existing environments** | Do not move until you upgrade them. Pinning `mcp>=1.20,<2.0` yourself remains supported. |
| **Existing environments** | Do not move until you upgrade them. Pinning `mcp>=1.22,<2.0` yourself remains supported. mcp 1.20 and 1.21 fail to import with pydantic 2.14 or later, which removed a private helper they import; keep pydantic below 2.14 if you must stay on them. |
| **3.x** | Outside the pin. |

The protocol version is negotiated by the SDK at `initialize`, not fixed by Forge. A client built on that `mcp 2.3.0` was offered `2025-11-25` by both servers.
Expand Down
2 changes: 1 addition & 1 deletion docs/walkthrough/mcp-output-port.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -343,7 +343,7 @@ declared capabilities under `experimental.fluid`, which both SDK generations par
```

An existing environment does not move until it is upgraded, and pinning
`mcp>=1.20,<2.0` still works. None of this applies once authentication is enforced:
`mcp>=1.22,<2.0` still works (mcp 1.20 and 1.21 fail to import with pydantic 2.14 or later). None of this applies once authentication is enforced:
verified JWT claims replace self-attestation outright, and with `FLUID_MCP_AUTH_TOKEN` set the self-attested values are dropped.
:::

Expand Down
Loading