The SnapLogic MCP Server feature enables you to create an MCP server in your SnapLogic environment to connect to your tool pipelines. It is in currently in Preview.

The SnapLogic MCP Server consists of three core components:

• Server Pipeline – This defines the overall behavior of the server.

• Tool Pipelines – These encapsulate individual tools or tasks the server will expose.

• MCP Triggered Task – A special type of Triggered Task used to publish the MCP Server.

To create and publish an MCP Server, users must:

1. Create a server pipeline

2. Connect the MCP Server pipeline to one or more tool pipelines

3. Register it using an MCP-type Triggered Task

Once published, the server can be accessed by the clients who support MCP Streamable HTTP and SSE transport.

This guide will walk you through the process step-by-step.

• The MCP Server preview version must run on a specific Snaplex with the appropriate version.

• For MCP servers running on Groundplexes, clients need direct access permission to the Groundplex node either through a public IP address or a load balancer.

• Web-based clients (such as OpenAI Dashboard) may not work due to uncontrollable request origins.

Before you start setting up an MCP Server, please ensure the following: 

1. Your Org is enabled with the MCP server feature. 

   • You can verify this by checking whether the Manager -> Features page includes MCP Server.

2. Tool pipelines must already exist and be accessible to the MCP server pipeline.

3. If you want to start demonstrating the SnapLogic MCP Server from creating a Groundplex, you need at least Env Admin permissions for an Org.

4. Make sure the account cc+{org_name}@snaplogic.com has been added to the Org and been set as Env Admin. 

5. In Admin Manager > Snaplexes, click Add Snaplex and enter the required information.

6. In the Node properties tab, scroll down to the Global properties section, and add jcc.enable_mcp_server=true in the Snaplex node global properties, as shown below.
   
   

   Open

   

7. To use the Cloudplex, set the load balancer. For Groundplexes, a self-signed certificates may not be accepted by some MCP clients, such as Claude. The Load balancer URL must use a valid TLS certificate. Cloudplexes have valid TL certificat with CA-Signed certs.

8. MCP Client (Optional, for Testing).

• To test your server after setup, you may use the MCP Client, for example, Claude Desktop App or MCP Inspector.

• You can also use any client that supports MCP transport, but note that since SSE transport is being deprecated, some clients may encounter unknown issues when connecting via SSE. 

The Server Pipeline is based on a fixed template. You only need to configure the Multi-pipeline Function Generator according to their specific toolset requirements.

No other modifications to the pipeline structure are necessary.

You can create the Server Pipeline in one of following three ways:

1. Copy – Copy all the pipelines directly from the example project into your own project. 

2. Manually – Build the pipeline following the template structure.

3. Import – Use the example file which you can download at the following link:
   

Open

Find and select tool pipelines from your Org.

1. Open the Multi Pipeline Function Generator Snap settings.

2. Click and select the tool pipelines from the pipeline picker.

Once the Server Pipeline has been created, the next step is to register it as an MCP Server by creating a special Triggered Task.

1. Create a Triggered Task from the Server Pipeline.

2. When selecting your Snaplex, make sure you choose a Snaplex with version of 4.PLAT_mcp-37764 - 4.43.1.0 MCP Update (Restricted Distribution). This is important because the MCP Server code on the Snaplex JCC service is released as a Restricted WAR file patch. 

   • On the UAT pod, please use MCP_groundplex. 

   • For HTTP Stremable transport, the load balancer is needed and the load balancer url need to be set in the Snaplex settings.

The load balancer URL must use a valid TLS certificate. Self-signed certificates will not be accepted by some MCP clients such as Claude.

3. Click the Register as MCP Server checkbox.

4. (Optional) Check Enable authentication to do the following:

   • Bind a Bearer Token to the Triggered Task.

   • Require clients to authenticate when connecting to the MCP Server.

5. Once the triggered task is created, you can view the following information in the Task Details page:

   • The MCP Server URL

   • If authentication is enabled, the Bearer Token.

Open

Open

The MCP Server URL is generated based on the Snaplex configuration in your task settings. The URL structure and access requirements depend on your deployment type.

Access requirements vary based on your deployment scenario:

• Access Level: Publicly accessible by default

• Configuration Required: None

• Usage: Connect from any MCP client using the URL provided in the Task Details page

• Best For: Users who need simple setup and broad accessibility

• Access Level: Configurable through load balancer

• Configuration Required: Set up access control rules on your Groundplex load balancer based on your security requirements

• Example: To use ChatGPT as an MCP client, whitelist <https://chat.openai.com> in your load balancer configuration

• Best For: Organizations requiring controlled access while supporting multiple clients

The generated URL includes the node's hostname, which has important network accessibility implications:

• Same Local Network:

  • The URL can be used as-is if the MCP client and server are on the same local network

  • No additional configuration needed

• External Client (running outside the Groundplex node environment):

  • The hostname cannot be used directly

  • Required Configuration Steps:

    1. Manually replace the hostname in the URL with the server's public IP address

    2. Add your MCP client's IP address or domain to the server's firewall whitelist

    3. Ensure proper network configuration for external access

• Best For: Internal networks or testing environments where direct node access is available

Once you have the MCP Server URL (for example, http://example.com:8090/mcp/xyz/mcp, http://example.com:8090/mcp/xyz/sse), you can connect to it using any MCP-compatible client. Below are two examples using common tools. 

If you’re using the Claude desktop application for interacting with MCP servers, follow these steps:

1. Open the Claude app.

2. Navigate to Settings > Developer > Edit Config

3. Paste the following config to the config file (claude_desktop_config.json) showed up.

For the case of Authentication enabled, you will need to add the following bearer token after --allow-http

4. Save and reboot Claude desktop app, you should now see the server connection appear in your Claude client, ready for interaction.
   
   

   Open

   

The MCP Inspector is a lightweight internal tool designed for testing and debugging MCP server connections. You can find more detailed usage instructions for it here.

Steps:

1. Run npx @modelcontextprotocol/inspector/ in your terminal to open the MCP inspector tool. 

2. In the Connection panel, enter the full URL:

http://example.com:8090/mcp/xyz/mcp

3. (If authentication is enabled) Paste the Bearer Token into the Authorization field.

4. Click Connect.

5. Once connected, you can:

• List available functions on the server

• Send function calls to the server

Open

Open

Due to the current limitations of MCP server SSE transport, the MCP client needs to be able to directly access the Snaplex node to create and maintain the SSE tunnel. Therefore, the MCP server can only run on a Groundplex. 

For the general method of deploying Groundplex, please refer to this document and its subarticles: Groundplexes

• Load Balancer Requirement: A load balancer is required for Cloudplex, or for Groundplex deployments where no specific node is selected.

• Access Control: The node should either:

  • allow requests from any source, or

  • explicitly allow the machines running MCP Clients.

• Local Clients vs. Web Clients:

  • Local MCP Clients, such as Claude, MCP Inspector, Roo Code, can connect normally as long as their machines are permitted by the Groundplex node.

  • Web-based clients, such as OpenAI Dashboard, might fail to connect, since their requests originate from the web side, where access permissions cannot be controlled.

Since the MCP server is still in the restricted WAR file patch release mode, you need to select version 4.PLAT_mcp-36959-4.43DEV in the Snaplex version.

Open

In the Node properties tab

• To allow the node to receive requests from outside, you need to set the HTTP interface to Any interface(0.0.0.0).

• The jcc.enable_mcp_server=true need to be added in the Global Properties.

Open

You need to maintain the hostname of the Groundplex node and manually replace the invalid host in the MCP URL with the Groundplex node’s public IP address, as required. Although you can set a Groundplex node’s load balancer in the Snaplex settings page to replace the invalid hostname in the URI, but only one Groundplex node can exist under that load balancer. When multiple nodes exist under a load balancer, there’s an issue where client sessions cannot be shared between the nodes.

Open

Since HTTPS requests are usually directed to port 8081 of the load balancer, and the MCP adapter on JCC has not implemented the business logic for handling HTTPS, the MCP server URL currently only supports HTTP. You can allow HTTP URLs by adding arguments such as “–allow-http” to the MCP client. However, this may result in certain clients that do not support enabling HTTP mode being unable to access the SnapLogic MCP server.

Open

• SnapLogic MCP Support