modelcontextprotocol/python-sdk
Watch
1
0
Fork
You've already forked python-sdk
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: stop presenting the in-memory client as the way to connect (#3443)

Browse source
This commit is contained in:
Max 2026-09-05 04:15:58 +01:00 • committed by GitHub
commit 7bb486a10f
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 803 additions and 598 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/get-started/testing.md
View file

@ -1,8 +1,8 @@
# Testing
The Python SDK ships a `Client` class with an **in-memory transport**: pass it your server object and it connects to it directly.
The SDK's `Client` class, the same one that connects to a URL or launches a subprocess, also connects **in memory**: pass it your server object and it talks to it directly.
No subprocess. No port. No transport at all. It's the same idea as FastAPI's `TestClient`.
No subprocess. No port. Nothing on a wire. It's the same idea as FastAPI's `TestClient`.
## Basic usage
@ -91,7 +91,7 @@ instead of the sanitised one.
Leave it on in tests. It has no meaning in production code.
## In-process by default
## Era-neutral by default
!!! note
`Client(mcp)` connects in-process and is **era-neutral** by default: it probes the server and