Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 22:23:50 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #4494] [BUG]: MCP SSE does not send configured headers #2862

New Issue
Closed
opened 2026-02-22 18:31:34 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 18:31:34 -05:00
Owner
Copy Link
Copy Source

Originally created by @ppil on GitHub (Oct 5, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4494

How are you running AnythingLLM?

Docker (local)

What happened?

I need to add a bearer token to SSE MCP requests for an internally hosted, yet remote to AnythingLLM, MCP server. Added the appropriate config (redacted below), and it was getting 401 unauthorized from my server. Tested from the LLM host via Curl with an explicit header and that works. Read the code behind making SSE requests from config through to the SDK, and the header from config should get passed, but isn't for some reason

{
  "mcpServers": {
     "derp": {
        "type": "sse",
        "url": "https://derp/mcp_server/sse"
        "headers":{
            "Authorization": "Bearer loremipsumnottodayhackerman"
        }
     }
  }
}

Tracked this down to an MCP SDK bug that was fixed in release 1.12.1. Looks like we're using an old version that hasn't gotten this bugfix yet...

I popped into the docker container and manually upgraded the server to the lastest @modelcontextprotocol/sdk (1.19.1) and it connected to my remote MCP server with no issue.

Requesting that this dependency be upgraded.

Are there known steps to reproduce?

Try to use a bearer token to add an SSE-based MCP server

Originally created by @ppil on GitHub (Oct 5, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4494 ### How are you running AnythingLLM? Docker (local) ### What happened? I need to add a bearer token to SSE MCP requests for an internally hosted, yet remote to AnythingLLM, MCP server. Added the appropriate config (redacted below), and it was getting 401 unauthorized from my server. Tested from the LLM host via Curl with an explicit header and that works. Read the code behind making SSE requests from config through to the SDK, and the header from config should get passed, but isn't for some reason ``` { "mcpServers": { "derp": { "type": "sse", "url": "https://derp/mcp_server/sse" "headers":{ "Authorization": "Bearer loremipsumnottodayhackerman" } } } } ``` Tracked this down to an MCP SDK [bug](https://github.com/modelcontextprotocol/typescript-sdk/issues/317) that was [fixed](https://github.com/modelcontextprotocol/typescript-sdk/pull/538) in release [1.12.1](https://github.com/modelcontextprotocol/typescript-sdk/releases/tag/1.12.1). Looks like we're using an old version that hasn't gotten this bugfix yet... I popped into the docker container and manually upgraded the server to the lastest @modelcontextprotocol/sdk (1.19.1) and it connected to my remote MCP server with no issue. Requesting that this dependency be upgraded. ### Are there known steps to reproduce? Try to use a bearer token to add an SSE-based MCP server
yindo added the possible bug label 2026-02-22 18:31:34 -05:00
yindo closed this issue 2026-02-22 18:31:34 -05:00
yindo changed title from [BUG]: MCP SSE does not send configured headers to [GH-ISSUE #4494] [BUG]: MCP SSE does not send configured headers 2026-06-05 14:48:56 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2862
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?