How to configure SSE

[benamazing]

I deployed the MCP server in SSE mode and configured in my AI client (Cursor & Cherry Studio), but not working. Both didn't perform the MCP tools actually. What's the problem?

[sooperset]

Hi, @benamazing Did you run the SSE server according to the configuration specified in the readme? Does stdio work properly? If you could provide specific details about what issues you're experiencing, it would be helpful in resolving the problem.

[kwanzeon]

I have the same issue. Runs fine in Docker in stdio mode. Switching to sse mode:

"atlassian": {
  "command": "docker",
  "args": [
    "run",
    "--name",
    "atlassian-mcp",
    "-i",
    "--env-file",
    "/Users/username/.cursor/.atlassian_mcp.env",
    "-p",
    "8080:8080",
    "ghcr.io/sooperset/mcp-atlassian:latest",
    "--transport",
    "sse",
    "--port",
    "8080",
    "-vv"
  ]
},

The container starts then gracefully shuts down. Version 0.11.9. Nothing else running on port 8080. Log here:

2025-07-10 18:36:33.314 | DEBUG - mcp-atlassian - Logging level set to: DEBUG
2025-07-10 18:36:33.315 | DEBUG - mcp-atlassian - Logging stream set to: stderr
2025-07-10 18:36:33.315 | DEBUG - mcp-atlassian - Attempting to load environment from default .env file if it exists
2025-07-10 18:36:33.315 | DEBUG - mcp-atlassian - Final transport determined: sse
2025-07-10 18:36:33.315 | DEBUG - mcp-atlassian - Final port for HTTP transports: 8080
2025-07-10 18:36:33.315 | DEBUG - mcp-atlassian - Final host for HTTP transports: 0.0.0.0
2025-07-10 18:36:33.315 | DEBUG - mcp-atlassian - Final path for Streamable HTTP: FastMCP default
2025-07-10 18:36:34.569 | DEBUG - mcp.server.lowlevel.server - Initializing server 'Confluence MCP Service'
2025-07-10 18:36:34.569 | DEBUG - mcp.server.lowlevel.server - Registering handler for ListToolsRequest
2025-07-10 18:36:34.569 | DEBUG - mcp.server.lowlevel.server - Registering handler for CallToolRequest
2025-07-10 18:36:34.569 | DEBUG - mcp.server.lowlevel.server - Registering handler for ListResourcesRequest
2025-07-10 18:36:34.569 | DEBUG - mcp.server.lowlevel.server - Registering handler for ReadResourceRequest
2025-07-10 18:36:34.569 | DEBUG - mcp.server.lowlevel.server - Registering handler for PromptListRequest
2025-07-10 18:36:34.570 | DEBUG - mcp.server.lowlevel.server - Registering handler for GetPromptRequest
2025-07-10 18:36:34.570 | DEBUG - mcp.server.lowlevel.server - Registering handler for ListResourceTemplatesRequest
2025-07-10 18:36:34.586 | DEBUG - mcp.server.lowlevel.server - Initializing server 'Jira MCP Service'
2025-07-10 18:36:34.586 | DEBUG - mcp.server.lowlevel.server - Registering handler for ListToolsRequest
2025-07-10 18:36:34.586 | DEBUG - mcp.server.lowlevel.server - Registering handler for CallToolRequest
2025-07-10 18:36:34.586 | DEBUG - mcp.server.lowlevel.server - Registering handler for ListResourcesRequest
2025-07-10 18:36:34.586 | DEBUG - mcp.server.lowlevel.server - Registering handler for ReadResourceRequest
2025-07-10 18:36:34.586 | DEBUG - mcp.server.lowlevel.server - Registering handler for PromptListRequest
2025-07-10 18:36:34.586 | DEBUG - mcp.server.lowlevel.server - Registering handler for GetPromptRequest
2025-07-10 18:36:34.586 | DEBUG - mcp.server.lowlevel.server - Registering handler for ListResourceTemplatesRequest
2025-07-10 18:36:34.617 | DEBUG - mcp.server.lowlevel.server - Initializing server 'Atlassian MCP'
2025-07-10 18:36:34.617 | DEBUG - mcp.server.lowlevel.server - Registering handler for ListToolsRequest
2025-07-10 18:36:34.617 | DEBUG - mcp.server.lowlevel.server - Registering handler for CallToolRequest
2025-07-10 18:36:34.617 | DEBUG - mcp.server.lowlevel.server - Registering handler for ListResourcesRequest
2025-07-10 18:36:34.617 | DEBUG - mcp.server.lowlevel.server - Registering handler for ReadResourceRequest
2025-07-10 18:36:34.617 | DEBUG - mcp.server.lowlevel.server - Registering handler for PromptListRequest
2025-07-10 18:36:34.617 | DEBUG - mcp.server.lowlevel.server - Registering handler for GetPromptRequest
2025-07-10 18:36:34.617 | DEBUG - mcp.server.lowlevel.server - Registering handler for ListResourceTemplatesRequest
2025-07-10 18:36:34.622 | INFO - mcp-atlassian.server.main - Added /healthz endpoint for Kubernetes probes
2025-07-10 18:36:34.622 | INFO - mcp-atlassian - Starting server with SSE transport on http://0.0.0.0:8080/sse
2025-07-10 18:36:34.622 | DEBUG - mcp-atlassian.utils.lifecycle - SIGPIPE handler registered
2025-07-10 18:36:34.622 | DEBUG - mcp-atlassian - Starting asyncio event loop...
2025-07-10 18:36:34.622 | DEBUG - mcp-atlassian - Running server for sse transport without stdin monitoring
2025-07-10 18:36:34.622 | DEBUG - asyncio - Using selector: EpollSelector
2025-07-10 18:36:34.622 | DEBUG - mcp.server.sse - SseServerTransport initialized with endpoint: /messages/
2025-07-10 18:36:34.625 | [07/10/25 22:36:34] INFO Starting MCP server 'Atlassian MCP' server.py:783
2025-07-10 18:36:34.625 | with transport 'sse' on
2025-07-10 18:36:34.625 | http://0.0.0.0:8080/sse
2025-07-10 18:36:34.625 | INFO - FastMCP.fastmcp.server.server - Starting MCP server 'Atlassian MCP' with transport 'sse' on http://0.0.0.0:8080/sse
2025-07-10 18:36:34.663 | INFO: Started server process [1]
2025-07-10 18:36:34.663 | INFO: Waiting for application startup.
2025-07-10 18:36:34.663 | INFO: Application startup complete.
2025-07-10 18:36:34.664 | INFO: Uvicorn running on http://0.0.0.0:8080 (Press CTRL+C to quit)
2025-07-10 18:37:32.423 | INFO: Shutting down
2025-07-10 18:37:32.532 | ERROR: Cancel 0 running task(s), timeout graceful shutdown exceeded
2025-07-10 18:37:32.532 | INFO: Waiting for application shutdown.
2025-07-10 18:37:32.533 | INFO: Application shutdown complete.
2025-07-10 18:37:32.533 | INFO: Finished server process [1]
2025-07-10 18:37:32.535 | INFO - mcp-atlassian.utils.lifecycle - Server stopped, flushing output streams...
2025-07-10 18:37:32.535 | DEBUG - mcp-atlassian.utils.lifecycle - Output streams flushed, exiting gracefully

[LazySeaSeal]

Were you able to find a solution? I'm open to discussing it if you'd like.

[kwanzeon]

I have not found a solution yet. I'm on vacation until mid-August but I'd be happy to discuss when I return. I'll reach out at that time. Thanks for the response.

…

________________________________ From: Jlassi Achraf ***@***.***> Sent: Thursday, July 24, 2025 6:05:41 AM To: sooperset/mcp-atlassian ***@***.***> Cc: kwanzeon ***@***.***>; Comment ***@***.***> Subject: Re: [sooperset/mcp-atlassian] How to configure SSE (Discussion #352) Were you able to find a solution? I'm open to discussing it if you'd like. — Reply to this email directly, view it on GitHub<#352 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALWMOQHYEYO25PZF4N3NJ733KDK2LAVCNFSM6AAAAAB4FBXOQKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOBXG43TANI>. You are receiving this because you commented.Message ID: ***@***.***>

[kwanzeon]

Back from vacation today. Followed the instructions in the README and it worked right away in cursor. Specifically: Start the server - # For SSE transport docker run --rm -p 9000:9000 \ --env-file /path/to/your/.env \ ghcr.io/sooperset/mcp-atlassian:latest \ --transport sse --port 9000 -vv Configure in cursor mcp.json - { "mcpServers": { "mcp-atlassian-http": { "url": "http://localhost:9000/sse" } } } Thanks for the support!

…

________________________________ From: Kevin O'Conner ***@***.***> Sent: Friday, July 25, 2025 12:48 AM To: sooperset/mcp-atlassian ***@***.***>; sooperset/mcp-atlassian ***@***.***> Cc: Comment ***@***.***> Subject: Re: [sooperset/mcp-atlassian] How to configure SSE (Discussion #352) I have not found a solution yet. I'm on vacation until mid-August but I'd be happy to discuss when I return. I'll reach out at that time. Thanks for the response.

________________________________ From: Jlassi Achraf ***@***.***> Sent: Thursday, July 24, 2025 6:05:41 AM To: sooperset/mcp-atlassian ***@***.***> Cc: kwanzeon ***@***.***>; Comment ***@***.***> Subject: Re: [sooperset/mcp-atlassian] How to configure SSE (Discussion #352) Were you able to find a solution? I'm open to discussing it if you'd like. — Reply to this email directly, view it on GitHub<#352 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALWMOQHYEYO25PZF4N3NJ733KDK2LAVCNFSM6AAAAAB4FBXOQKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOBXG43TANI>. You are receiving this because you commented.Message ID: ***@***.***>