gitcnd
April 9, 2025, 2:20am
1
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
4 Likes
DrPhil
April 11, 2025, 9:15pm
2
+1
makes it unusable for my usecase
ttys3
April 12, 2025, 3:08pm
3
+1
makes it unusable for my usecase. for example: http mcp server
@deanrie please forwarded this to the team too, thanks
ttys3
April 12, 2025, 3:08pm
4
I want also refer this bug about mcp: Mcp client does not support `roots/list` - #3 by ttys3
guys, please +1 for me, lets make Cursor mcp client impementation better
+1 how will I send parameters to a hosted MCP server, MCP is moving towards hosted team is building fast and this has halted our progress
Hey,
when can we expect these fixes to come out? I apologise for asking such question, but I’m not sure if I should start working on a workaround for this issue, or just wait for the update to come out, since this issue is currently blocking us.
Thanks in advance
Do you have an expected resolution time for this issue?
gitcnd:
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
Has anyone gotten any indication if this is in the pipeline?