-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add sse accept header #178
Conversation
I don't think this change should be needed since my understanding is that the Is there a specific issue you're trying to address with this change? |
@olaservo in this project, we pass |
in my case, i using nchan.io as sequenceDiagram
MCP Client->>NCNAN: connect
activate NCNAN
MCP Client-->>NCNAN: jsonrpc request
NCNAN-->>FastAPI: nchan_publisher_upstream_request
FastAPI-->>MCP Server: call_tool(name, args)
MCP Server-->>FastAPI: result
FastAPI-->>NCNAN: jsonrpc response
NCNAN-->> MCP Client: jsonrpc response
MCP Client-->>NCNAN: jsonrpc request
NCNAN-->>FastAPI: nchan_publisher_upstream_request
FastAPI-->>MCP Server: call_tool(name, args) in backend
MCP Server-->>NCNAN: push notification
NCNAN-->> MCP Client: notification
MCP Server-->>NCNAN: push jsonrpc response
NCNAN-->> MCP Client: jsonrpc response
NCNAN->> MCP Client: close
deactivate NCNAN
|
@lloydzhou This feels like a workaround for a problem that exists with nchan. Is it possible to make a PR there to fix the issue? |
@cliffhall https://github.com/modelcontextprotocol/inspector/blob/main/server/src/index.ts#L82C7-L82C22 https://github.com/modelcontextprotocol/typescript-sdk/blob/main/src/client/sse.ts#L115 |
@lloydzhou thanks for clarifying, I see what you mean now. Since we're using a custom fetch (which is filtering the headers to forward) we're not sending the Accept header by default. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @lloydzhou I think this is good to merge, however could you clarify a little more about how you tested this?
@lloydzhou looks like you need to fix some formatting issues, could you run the following and also update your branch:
|
|
Motivation and Context
How Has This Been Tested?
Breaking Changes
Types of changes
Checklist
Additional context