MCP Endpoint 404

Need help
1

Right now Activepieces end point for MCP server is

/api/v1/mcp/xxxx/sse
/api/v1/mcp/messages

With the latest changes of @modelcontextprotocol/sdk in version 1.11.3, which preserve custom paths in SSE endpoint URLs (fix: preserve custom paths in SSE endpoint URLs by bhosmer-ant · Pull Request #466 · modelcontextprotocol/typescript-sdk · GitHub), the Activepieces /messages endpoint now becomes impossible to connect. It will give a 404 error because it is trying to connect via /api/v1/mcp/xxxx/messages

Will there be any fix for this?

2

Hi @Jackson_Lew

We enrolled an update with /messages but we rolled it back, currently we are back to /sse only until we figure out the right way to do it.

3

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.