Luna W.

This is the output of you server pipeline, correct? The output will be pasred to MCP required format by a component called "SnapLogic MCP adapter" running on the jcc node. The adapter handles tasks that users do not need to worry about, such as translating requests and responses. You should be able to connect to your MCP server using any popular MCP client. This demonstrates that the responses sent back by the server are fully compliant with the MCP protocol andJSON-RPC standard.

May I ask what part is not compliant? Have you encountered any error messages?

In addition to the two points mentioned above, I noticed you have a load balancer. After solving the current issue, you can try not selecting a specific node when creating the MCP server. In this case, the server URL will automatically use the load balancer's URL, avoiding the need for manual replacement. As long as the network where your MCP client is located can access the load balancer, this approach should work.

Possible solutions: 1. Check your node's JCC version to ensure you are using 37764 - 4.43.1.0 MCP Update as in the screenshot. The node in the screenshot is random choice. 2. Replace the host:port portion in the MCP server URL with this node's public IP. You can find it in the following path: Waffle Menu → Monitor → Infrastructure → (click on the relevant node) → Additional Details → Public IP. The reason is that the host:port is often not publicly accessible. Therefore, you need to fill in the public IP. The url will looks like: https://{node's public ip}/mcp/{server id}/mcp

Hi Omar, has it never worked before, or did it stop working after a certain operation? This information will help us debug the issue.

If I am able to connect from MCP inspector tool to SL then in that case, MCP tool will be the MCP client & Snaplogic act as MCP server right?

Yes, MCP inspector is an MCP client. You can use it to connect to the MCP Servers built in SnapLogic.

And if i need to connect to another MCP server then configuring the MCP SSE or HTTP account at Snaplogic end which acts as MCP client & the target will be the MCP server? (edited

Yes, the MCP Function Generator Snap and MCP Invoke Snap and their MCP SEE/HTTP account acts as an MCP client to allow you to connect to other MCP servers whether they are built in SnapLogic or not. Basically, SnapLogic provides both the MCP client and the MCP server capabilities.

Hi Imaya,