René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Addition of client request headers to MCP tools","articleBody":"**Is your feature request related to a problem? Please describe.**\nCurrently, the MCP Python SDK does not expose client request headers to MCP tools. This makes it difficult to implement user-specific access controls or contextual logic within a single server, especially for database queries where permissions are critical. As a result, we’re forced to consider inefficient solutions like deploying separate MCP instances for different clients.\n\n**Describe the solution you'd like**\nExpose client request headers to MCP tools (through the Context object maybe?) so that logic can be adjusted based on user context (e.g., access tokens, roles, tenant IDs). This would allow a single MCP server to securely handle multiple clients and enforce proper access control directly within the tools.\n\n**Describe alternatives you've considered**\n- Running separate MCP servers per client (inefficient and hard to scale).\n- Passing user data through request bodies (insecure because of LLM interference risk).\n- Adding custom middleware outside of MCP (adds unnecessary complexity, and still not accessible within tools).\n\n**Additional context**\nThis feature would improve multi-tenant support and align with standard API practices for handling authentication and authorization.","author":{"url":"https://github.com/rusenbb","@type":"Person","name":"rusenbb"},"datePublished":"2025-05-09T12:40:21.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/674/python-sdk/issues/674"}