You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(mcp): SSE endpoint config mismatch and incorrect server name in MCP router #1673
WithSSEEndpoint("/answer/api/v1/mcp/see") contains a typo (see → sse) and does not match the actual mount path GET /answer/api/v1/mcp/sse. It currently "works" only because SSEHandler()/MessageHandler() are mounted manually and the configured path is never validated by mcp-go v0.43.2; the value is misleading and will break anything relying on CompleteSsePath() (e.g. URL resolution, health checks, or future path validation).
The endpoint strings are duplicated as raw literals instead of shared constants, so the SSE config, the gin mount paths, and the client-facing endpoint event can drift apart silently.
The server is registered as "Answer Enterprise MCP Server", which is not appropriate naming for the Apache Answer project.
To Reproduce
Read internal/router/mcp_router.go and compare WithSSEEndpoint("/answer/api/v1/mcp/see") with the actual mount path r.GET("/mcp/sse", ...).
Start a site with MCP enabled in the admin settings.
Connect any MCP client to http://<host>/answer/api/v1/mcp/sse and check the server name reported during initialization: it shows Answer Enterprise MCP Server.
Expected behavior
The configured SSE endpoint should exactly match the actual mount path (/answer/api/v1/mcp/sse), endpoint strings should be defined as shared constants to avoid drift, and the MCP server should identify itself as Apache Answer MCP Server.
Activity
fix(mcp): correct SSE endpoint path and server name in MCP router (#1680
LinkinStars commentedon Nov 19, 2026
Fixed by #1680.