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 #4161] [BUG]: Unable to connect to Github or Atlassian MCP via SSE #2648

New Issue
Closed
opened 2026-02-22 18:30:36 -05:00 by yindo · 1 comment
yindo commented 2026-02-22 18:30:36 -05:00
Owner
Copy Link
Copy Source

Originally created by @devtanna on GitHub (Jul 16, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4161

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

Hello all,
As per the documentation SSE MCP's are supported but when I add them, they are getting recognized but for each of them I get a 401 Unauthorized error. Failed to start MCP server: Atlassian MCP [401] SSE error: Non-200 status code (401)

Is there some setup I am missing?

The expectation was that there would be an oauth flow triggered to connect these servers.

Are there known steps to reproduce?

This is my mcp config:

{
  "mcpServers": {
    "GitHub MCP": {
        "url": "https://api.githubcopilot.com/mcp/",
        "type": "sse"
    },
    "Atlassian MCP": {
        "url": "https://mcp.atlassian.com/v1/sse",
        "type": "sse"
    }
  }
}
Originally created by @devtanna on GitHub (Jul 16, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4161 ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? Hello all, As per the documentation SSE MCP's are supported but when I add them, they are getting recognized but for each of them I get a 401 Unauthorized error. `Failed to start MCP server: Atlassian MCP [401] SSE error: Non-200 status code (401)` Is there some setup I am missing? The expectation was that there would be an oauth flow triggered to connect these servers. ### Are there known steps to reproduce? This is my mcp config: ``` { "mcpServers": { "GitHub MCP": { "url": "https://api.githubcopilot.com/mcp/", "type": "sse" }, "Atlassian MCP": { "url": "https://mcp.atlassian.com/v1/sse", "type": "sse" } } } ```
yindo added the possible bug label 2026-02-22 18:30:36 -05:00
yindo closed this issue 2026-02-22 18:30:36 -05:00
yindo commented 2026-02-22 18:30:36 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jul 16, 2025):

The expectation was that there would be an oauth flow triggered to connect these servers.

We do not trigger or pass through an OAuth flow. So in order to facilitate this you should be using env configs for the credentials to connect

@timothycarambat commented on GitHub (Jul 16, 2025): > The expectation was that there would be an oauth flow triggered to connect these servers. We do not trigger or pass through an OAuth flow. So in order to facilitate this you should be using `env` configs for the credentials to connect
yindo changed title from [BUG]: Unable to connect to Github or Atlassian MCP via SSE to [GH-ISSUE #4161] [BUG]: Unable to connect to Github or Atlassian MCP via SSE 2026-06-05 14:47:43 -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#2648
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?