# The mcp sse env parameter cannot be passed **URL:** \ **Category:** Bug Reports\ **Created:** [April 27, 2025, 8:17am UTC](https://forum.cursor.com/t/the-mcp-sse-env-parameter-cannot-be-passed/84272 "2025-04-27T08:17:36Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![jiangyang-yu](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jiangyang-yu/32/50347_2.png) [@jiangyang-yu](https://forum.cursor.com/u/jiangyang-yu)\ **Post date:** [April 27, 2025, 8:17am UTC](https://forum.cursor.com/t/the-mcp-sse-env-parameter-cannot-be-passed/84272/1 "2025-04-27T08:17:36Z")
The env parameter configured in MCP SSE mode does not take effect and is not filled into the parameters for calling during tool execution, which contradicts the official documentation. Similar issues have also been encountered by others Official document of cursor: [Cursor – Model Context Protocol](https://docs.cursor.com/context/model-context-protocol#configuring) -mcp-servers Other feedback posts: > [@Cursor MCP requests do not honour API-key provision to sse (only stdio works)](https://forum.cursor.com/t/cursor-mcp-requests-do-not-honour-api-key-provision-to-sse-only-stdio-works/76889): > > This is how MCP server configs are supposed to provide API keys to SSE endpoints: { "mcp": { "type": "sse", "url": "https://example.com/sse", "headers": { "Authorization": "Bearer YOUR\_API\_TOKEN" } } } But right now, your MCP implementation only understands “env” variables for stdio mcp servers. Please add the required support for sse This is very limited for the use of MCP, and we look forward to supporting it as soon as possible. ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [May 27, 2025, 8:18am UTC](https://forum.cursor.com/t/the-mcp-sse-env-parameter-cannot-be-passed/84272/2 "2025-05-27T08:18:09Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.