docs: add SSE transport deprecation warning for MCP integration #365
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add prominent deprecation warning box at the top of the page - Update MCP Server Capabilities table to mark SSE as deprecated - Update Tool Authorization section to clarify SSE is deprecated - Update Cursor deeplinks to use /mcp endpoints instead of /sse Related to: AI-2342 Co-Authored-By: Martin Vasko <Matovidlo2@gmail.com>
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Address PR feedback to use specific date instead of '3 months' Related to: AI-2342 Co-Authored-By: Martin Vasko <Matovidlo2@gmail.com>
Matovidlo
commented
Jan 27, 2026
integrate/mcp.md
Outdated
|
|
||
| <div class="alert alert-warning" role="alert"> | ||
| <i class="fas fa-exclamation-triangle"></i> | ||
| <strong>SSE Transport Deprecation:</strong> The SSE transport for MCP Server will be deprecated in 3 months. Please migrate to Streamable HTTP transport using <code>/mcp</code> endpoints instead of <code>/sse</code>. Streamable HTTP provides bidirectional streaming for improved performance and reliability. |
Contributor
Author
There was a problem hiding this comment.
Not 3 months but let's state 01.04.2026 the 1st of april
Contributor
There was a problem hiding this comment.
Updated to use the specific date 01.04.2026 instead of "3 months".
integrate/mcp.md
Outdated
| | Concept | Supported | Notes | | ||
| |-------------|-----------|--------------------------------------------------------------------------------------------------------| | ||
| | Transports | ✅ | Supports `stdio` and `Streamable HTTP` for client communication. | | ||
| | Transports | ✅ | Supports `stdio` and `Streamable HTTP` (recommended) for client communication. SSE is deprecated and will be removed in 3 months. | |
Contributor
Author
There was a problem hiding this comment.
Not 3 months but let's state 01.04.2026 the 1st of april
Contributor
There was a problem hiding this comment.
Updated to use the specific date 01.04.2026 instead of "3 months".
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Jira issue(s): AI-2342
Changes:
/mcpendpoints instead of/sseendpoints (also updated URL format to match connection-docs)This is part of a coordinated documentation update across three repositories (connection-docs, developers-docs, mcp-server) to communicate the SSE transport deprecation consistently.
Updates since last revision:
Human Review Checklist:
cursor://anysphere.cursor-deeplink/...) is correct/mcpendpointsLink to Devin run: https://app.devin.ai/sessions/3ddcad4977384d26b3e88e94e3e3778b
Requested by: Martin Vasko (@Matovidlo)
Release Notes
Justification, description
Adding deprecation notice for SSE transport in MCP integration documentation to inform developers about the upcoming migration to Streamable HTTP transport.
Plans for Customer Communication
This documentation update serves as the developer communication - users will see the deprecation warning when viewing MCP integration documentation.
Impact Analysis
Documentation-only change. No functional impact.
Deployment Plan
N/A
Rollback Plan
N/A
Post-Release Support Plan
N/A