StreamableHTTP transport: Server implementation #183
Copy link
Copy link
Closed
Description
There are a bunch of use cases to implement.
Each usecase should be covered with integration test.
1. Prompts
-
Capabilities spec
-
List Prompts spec
- Success
- Bad request
- Security - Allow
- Security - Deny
- Pagination
-
Get Prompt spec
-
List Change Prompts Notification spec
2. Resources
-
Capabilities spec
- Success
- Bad request
- Security - Allow
- Security - Deny
-
List Resources spec
- Success
- Bad request
- Security - Allow
- Security - Deny
- Pagination
-
Read Resource spec
- Success
- file:
- http:
- git:
- custom:
- Bad request
- Security - Allow
- Security - Deny
- Success
-
List Resource Templates spec
- Success
- Bad request
- Security - Allow
- Security - Deny
-
List Changed Notification spec
- Subscribe spec
- Bad request
- Security - Allow
- Security - Deny
-
Get Update Notification spec
3. Tools
-
Capabilities
-
Listing Tools spec
- Success
- Pagination
- Bad request
- Security - Allow
- Security - Deny
- Success
-
Call Tool spec
4. Logging
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
- StatusShow more project fieldsDone
- StatusShow more project fieldsDone
Activity
devcrocod commentedon Jul 21, 2025
#87
[-]Server implementation of Streamable transport[/-][+]StreamableHTTP transport: Server implementation[/+]test(integration): add Streamable HTTP transport support
test(integration): add Streamable HTTP transport support
test(integration): add Streamable HTTP transport support
[WIP]test(integration): Add Streamable HTTP transport integration tes…
test(streamable-http): add missing integration tests for pagination, …