-
Notifications
You must be signed in to change notification settings - Fork 1.3k
我用spring ai实现一个mcp server.服务起来后,一直无法访问/sse端点 #2732
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
Comments
为什么 1.0.0-M6 和 1.0.0-M7 混用,只用1.0.0-M7不就可以?yml 的配置也没有对齐。 |
你好,谢谢答复! 现在就是服务正常启动,但是启动的日志里面没有类似于tools register success这种,然后页面请求:http://localhost:8080/sse 无法请求到资源 |
sse use this |
服务端用这个 |
+1 |
I also encountered this issue, for a while I could successfully access /sse, but after that, I could no longer access it during startup, and it reported an error 404 |
服务端必须用这个,否则会报404,这是个bug org.springframework.ai |
I found the cause of the problem, adding the following dependency will not have this issue
If this dependency is introduced, this error will occur.
Although the official documentation recommends using spring-ai-starter-mcp-server-webflux for sse |
问题已解决,就是用kkxrrh的方法,pom.xml删除webflux依赖就可以了。 这应该是官方的问题,也不清楚为啥有这个问题,官方还要推荐webflux |
Please do a quick search on GitHub issues first, there might be already a duplicate issue for the one you are about to create.
If the bug is trivial, just go ahead and create the issue. Otherwise, please take a few moments and fill in the following sections:
Bug description
我用spring ai 实现 mcp server ,如果采用stdio的方式
打成jar包,然后用charry studio 配置,能够正常访问
但是通过spring ai 实现mcp server ,采用sse方式
服务正常启动,但是浏览器死活访问不到sse节点
localhost:8080/sse
通过postman也无法访问(控制台没有任何报错信息)
问题的原因是什么?
Environment
pom.xml:
Steps to reproduce

项目结构非常简单,服务也是正常启动
但是页面上就是一直无法访问:
localhost:8080/sse
通过postman也无法访问
Expected behavior
A clear and concise description of what you expected to happen.
Minimal Complete Reproducible example
Please provide a failing test or a minimal complete verifiable example that reproduces the issue.
Bug reports that are reproducible will take priority in resolution over reports that are not reproducible.
The text was updated successfully, but these errors were encountered: