Max Isbey

As of https://github.com/modelcontextprotocol/python-sdk/pull/1198 the SDK's FastMCP no longer pulls in configuration from environment variables. The service you implement can instead pull in configuration on its own from environment variables. Although...

Closing as @josiahdc's suggestion should solve the original issue. If it doesn't please feel free to re-open the issue.

Related: https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1545 Due to ongoing discussions around exactly what errors to use here we should wait on that before merging any fixes for this.

Thank you for the report! It would be great if you could provide some example code for the server/client with which shows the errors and what you'd expect, or hope...

This is a valid gap - we should match the TypeScript SDK's behavior here. **What the spec says:** > "Implementations SHOULD establish timeouts for all sent requests, to prevent hung...

There has been significant changes to the repo since this issue was last active including many more examples of how to use MCP. If this is still an issue please...

I'm unable to reproduce this. Additionally your code isn't a valid server, for example: ```python @app.call_tool() def test_tool(): ``` The `call_tool` decorator requires test_tool to take on two arguments, `name:...

> I didn't think this was going to be merged already. I've been thinking about this, and I'm unsure this is the cleanest approach. > > I think this API...

Closing as duplicate of #1190, which is tracking this issue. Thank you for doing some great root cause analysis, I've copied it in a comment over to #1190.

To add to this, neither the Typescript nor the Python SDK actually return -32002 by default. The Typescript SDK returns `-32602` already, whereas the Python SDK actually just returns `0`...