Add mcp.types as a permanent alias for mcp_types (#3190)

docs/servers/completions.md

@@ -21,7 +21,7 @@ Nothing here is about completions yet.
 
 Add **one** function decorated with `@mcp.completion()`:
 
-```python title="server.py" hl_lines="22-30"
+```python title="server.py" hl_lines="21-29"
 --8<-- "docs_src/completions/tutorial002.py"
 ```
 
@@ -91,7 +91,7 @@ You didn't list `completions` anywhere. The SDK saw the handler and declared the
 
 That's what `context` is for. It carries the arguments the user has **already resolved**:
 
-```python title="server.py" hl_lines="9-12 35-39"
+```python title="server.py" hl_lines="8-11 34-38"
 --8<-- "docs_src/completions/tutorial003.py"
 ```
 

docs/servers/handling-errors.md

@@ -41,7 +41,7 @@ The model is the one calling your tool. It picked the arguments. So a tool error
 
 Now swap `ValueError` for `MCPError`.
 
-```python title="server.py" hl_lines="1 3 15"
+```python title="server.py" hl_lines="1 3 14"
 --8<-- "docs_src/handling_errors/tutorial002.py"
 ```
 
@@ -56,7 +56,7 @@ Now swap `ValueError` for `MCPError`.
 
 * There is **no result**. No `content`, no `is_error`: nothing for the model to read.
 * The **host** application gets the error instead, the same way it would if the tool didn't exist at all.
-* `code`, `message`, and `data` arrive intact. `INVALID_PARAMS` is `-32602`; `mcp_types` exports it and the other JSON-RPC error codes (`INVALID_REQUEST`, `INTERNAL_ERROR`, ...) as constants so you never type a magic number.
+* `code`, `message`, and `data` arrive intact. `INVALID_PARAMS` is `-32602`; `mcp.types` exports it and the other JSON-RPC error codes (`INVALID_REQUEST`, `INTERNAL_ERROR`, ...) as constants so you never type a magic number.
 
 !!! check
     Same lookup, same miss, but now the call *raises* on the client side instead of returning:
@@ -127,7 +127,7 @@ It means a whole class of `raise` statements you don't write: don't re-validate
 * The deciding question: *could a smarter model have avoided this?* Yes -> exception. No -> `MCPError`.
 * `ResourceNotFoundError` from a resource handler -> the protocol's `-32602`, with the URI in `data`.
 * Bad arguments are rejected against the schema before your function runs; you don't `raise` for those.
-* `from mcp import MCPError`; the error-code constants come from `mcp_types`.
+* `from mcp import MCPError`; the error-code constants come from `mcp.types`.
 
 Errors handled. That is everything a server *exposes*. What every handler can read, and do back to the client while it runs, is the next section: **[Inside your handler](../handlers/index.md)**.
 

docs/servers/media.md

@@ -29,7 +29,7 @@ Two things to notice:
 * `structured_content` is `None`. An `Image` is content for the model to look at, not data for the application to parse: there is no output schema. (Contrast **[Structured Output](structured-output.md)**, where the return annotation *is* the schema.)
 
 !!! info
-    `ImageContent` and `AudioContent` live in `mcp_types`, right next to the `TextContent`
+    `ImageContent` and `AudioContent` live in `mcp.types`, right next to the `TextContent`
     that a plain `str` result becomes (**[Tools](tools.md)**). A tool result is a list of content blocks; `Image` and `Audio` are
     the shortest way to produce the two binary kinds.
 
@@ -85,7 +85,7 @@ A suffix it doesn't recognise falls back to `application/octet-stream`.
 
 An `Icon` is metadata, not content. It doesn't carry the image; it points at one with a URI, and a client may fetch it and show it next to your server's name, a tool, a resource, or a prompt.
 
-```python title="server.py" hl_lines="5-6 8 11 17"
+```python title="server.py" hl_lines="4-5 7 10 16"
 --8<-- "docs_src/media/tutorial004.py"
 ```
 

docs/servers/tools.md

@@ -142,7 +142,7 @@ There is nothing else to configure.
 
 Everything the SDK infers, you can override in the decorator:
 
-```python title="server.py" hl_lines="8-11"
+```python title="server.py" hl_lines="7-10"
 --8<-- "docs_src/tools/tutorial005.py"
 ```
 

docs/servers/uri-templates.md

@@ -215,7 +215,7 @@ return the protocol types yourself.
 
 For fixed URIs, keep a registry and dispatch on exact match:
 
-```python title="server.py" hl_lines="18 22 28"
+```python title="server.py" hl_lines="17 21 27"
 --8<-- "docs_src/uri_templates/tutorial004.py"
 ```
 
@@ -229,7 +229,7 @@ The template engine `MCPServer` uses lives in `mcp.shared.uri_template`
 and works on its own. You get the same parsing and matching; you wire
 up the routing and security policy yourself.
 
-```python title="server.py" hl_lines="14-17 23-26 30 34 46"
+```python title="server.py" hl_lines="13-16 22-25 29 33 45"
 --8<-- "docs_src/uri_templates/tutorial005.py"
 ```