mirror of
https://github.com/PrefectHQ/fastmcp.git
synced 2026-08-21 04:54:17 +02:00
03b62d2e3d* feat: handle error from the initialize middleware In some situation, the initialize middleware can check the status of the server and decide to raise an error. Example use case: in a FastMCPProxy, an initialization middleware overrides the on_initialize method and connect to the underlying proxied client. When client respond with error, I want to pass this error to the client. * docs update * test: use McpError assertions now that exception propagation is fixed - Update tests to catch McpError specifically instead of generic Exception - Remove commented-out code in low_level.py --------- Co-authored-by: Jeremiah Lowin <153965+jlowin@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| auth | ||
| composition.mdx | ||
| context.mdx | ||
| elicitation.mdx | ||
| icons.mdx | ||
| logging.mdx | ||
| middleware.mdx | ||
| progress.mdx | ||
| prompts.mdx | ||
| proxy.mdx | ||
| resources.mdx | ||
| sampling.mdx | ||
| server.mdx | ||
| storage-backends.mdx | ||
| tasks.mdx | ||
| tools.mdx | ||