d6a15f6d52
With v2 becoming the stable release, v1.x moves from the site root to /v1/ and stops deploying the site itself: the combined site is built and deployed from main, which builds this branch's docs into /v1/ via the new scripts/docs/build.sh. A `docs` CI job runs that same script, so a change that breaks the v1 docs fails on this branch rather than at main's next deploy. site_url and the package's Documentation URL move to /v1/ so canonical links, the sitemap, and llms.txt point at where these pages are actually served. The README and landing page now describe v1.x as the maintenance line and send new users to the v2 docs, and every install line pins `mcp<2` so a reader following these docs stays on the 1.x line now that an unpinned install selects 2.x.
1.6 KiB
1.6 KiB
Installation
The Python SDK is available on PyPI as mcp. These docs describe the v1.x maintenance line;
the <2 bound keeps you on it now that pip install mcp selects the 2.x stable release by default (the
v2 documentation covers that line):
=== "pip"
```bash
pip install "mcp<2"
```
=== "uv"
```bash
uv add "mcp<2"
```
The following dependencies are automatically installed:
httpx: HTTP client to handle HTTP Streamable and SSE transports.httpx-sse: HTTP client to handle SSE transport.pydantic: Types, JSON schema generation, data validation, and more.starlette: Web framework used to build the HTTP transport endpoints.python-multipart: Handle HTTP body parsing.sse-starlette: Server-Sent Events for Starlette, used to build the SSE transport endpoint.pydantic-settings: Settings management used in FastMCP.uvicorn: ASGI server used to run the HTTP transport endpoints.jsonschema: JSON schema validation.pywin32: Windows specific dependencies for the CLI tools.
This package has the following optional groups:
cli: Installstyperandpython-dotenvfor the MCP CLI tools.