Commit f695886
fix: support mcp 2.x, which breaks the client on a fresh install (#50)
pyproject pins "mcp>=1.9.0" with no upper bound, so any new install
resolves mcp 2.0.0 and every XpozClient() raises immediately:
ExceptionGroup: unhandled errors in a TaskGroup
ValueError: not enough values to unpack (expected 3, got 2)
Two breaking changes in mcp 2.0:
- streamable_http_client yields 2 values instead of 3, so the
"read, write, _ = streams" unpack fails.
- CallToolResult.isError was renamed to is_error.
Both are now handled without pinning, so the SDK works on 1.x and 2.x.
This is the same ValueError behind the errors seen across the live-API
test suites; tests/test_instagram.py goes from erroring to 13/13 passing
against the live API on mcp 2.0.0.
Claude-Session: https://claude.ai/code/session_011ekeWsNRndQwdgUE1SHqfe
Co-authored-by: claude-flow <ruv@ruv.net>1 parent 8e17202 commit f695886
1 file changed
Lines changed: 14 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
28 | 28 | | |
29 | 29 | | |
30 | 30 | | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
31 | 42 | | |
32 | | - | |
| 43 | + | |
33 | 44 | | |
34 | 45 | | |
35 | 46 | | |
| |||
71 | 82 | | |
72 | 83 | | |
73 | 84 | | |
74 | | - | |
| 85 | + | |
75 | 86 | | |
76 | 87 | | |
77 | 88 | | |
| |||
139 | 150 | | |
140 | 151 | | |
141 | 152 | | |
142 | | - | |
| 153 | + | |
143 | 154 | | |
144 | 155 | | |
145 | 156 | | |
| |||
0 commit comments