Diogo Santos

### Description ## Summary Tools and resources can currently return arbitrary content (text, JSON, etc.) that is forwarded directly to clients and often to LLMs. There is no built-in way...

### Description ### Context https://github.com/modelcontextprotocol/python-sdk/pull/1685 implemented server-wide tool execution timeouts with a default of 300 seconds. ### Motivation Some tools may need different timeout values: - Quick lookups: `get_weather()` -...

## Summary Implements baseline timeout behavior for MCP tool calls to prevent indefinite blocking. Closes #1374 ## Changes ### Server-Side Timeout - **Added REQUEST_TIMEOUT error code** (-32001) to `src/mcp/types.py` -...

### Description ## Summary The Python SDK currently uses a global `contextvars.ContextVar` (e.g. `request_ctx`) to hold per-request state for the server. This enables convenience helpers like `get_request_context()`, but it also...

### Description ### Summary The current Python SDK docs and examples focus on minimal, single-file servers (e.g. `weather.py` with all tools in one module). This is great for getting started...

Version-aware discovery for list_tools and related MCP APIs (Python SDK + protocol)

1

### Description ### Summary I’d like the MCP Python SDK (and, where appropriate, the underlying MCP protocol/server behavior) to support **version-aware discovery** for `list_tools` and potentially related discovery endpoints such...

### Summary With https://github.com/modelcontextprotocol/modelcontextprotocol/issues/986 (standardized tool-name format) and https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1575 (tool versioning) now shaping the MCP ecosystem, it would be helpful to add **clear, language-agnostic guidance** for how servers should combine:...