quickstart-resources/mcp-client-python
Repository files (latest commit first)
Filename Latest commit message Latest commit date
olaservo e83a860df2 Link the dated spec revision, not /draft
The surrounding sentence names 2026-07-28 as the revision that first allows
an array-rooted schema, but the link pointed at /draft, which moves on to
the next revision and stops matching the claim.

Came in with #164. The same fix is on the open Go, Rust, and Ruby branches.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-16 19:49:04 -07:00
..
.env.example Add .env. to the global gitignore, as well as .env.example to python client 2025-09-29 15:20:00 +02:00
.python-version Move mcp-client to mcp-client-python 2025-02-17 10:46:18 -08:00
client.py Add structured content to the Python weather server and client and update to v2 (#164) 2026-08-09 14:46:03 +02:00
pyproject.toml Add structured content to the Python weather server and client and update to v2 (#164) 2026-08-09 14:46:03 +02:00
README.md Link the dated spec revision, not /draft 2026-08-16 19:49:04 -07:00
uv.lock Add structured content to the Python weather server and client and update to v2 (#164) 2026-08-09 14:46:03 +02:00

An LLM-Powered Chatbot MCP Client written in Python

See the Build an MCP client tutorial for more information.

Structured content

call_tool validates every result against the tool's declared output schema, so the spec's client-side SHOULD needs no code here.

The two channels go to different readers: content is forwarded to the model, while structured_content is used as data — when a tool returns an array, the client counts its items rather than re-reading the prose. See Structured Content.

Client(transport, mode="auto") probes server/discover and falls back to the 2025-11-25 handshake; client.protocol_version reports which era you got. See Protocol versions.