MCP Invoke

Overview

Use this Snap to execute the operations you want the MCP server to perform. This Snap formats the generated results into a unified structure within SnapLogic.


MCP Invoke Snap

Prerequisites

  • A valid MCP Account with required fields provided.

Snap views

View Description Examples of upstream and downstream Snaps
Input This Snap has one document input view.
Output

This Snap supports exactly two document output views.

  • The First view is a passthrough of the input document for further processing downstream.
  • The second output view is the actual agent visualizer log that is being visualized.
Error

Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the pipeline by choosing one of the following options from the When errors occur list under the Views tab. The available options are:

  • Stop Pipeline Execution Stops the current pipeline execution when an error occurs.
  • Discard Error Data and Continue Ignores the error, discards that record, and continues with the remaining records.
  • Route Error Data to Error View Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

Snap settings

Legend:
  • Expression icon (): Allows using JavaScript syntax to access SnapLogic Expressions to set field values dynamically (if enabled). If disabled, you can provide a static value. Learn more.
  • SnapGPT (): Generates SnapLogic Expressions based on natural language using SnapGPT. Learn more.
  • Suggestion icon (): Populates a list of values dynamically based on your Snap configuration. You can select only one attribute at a time using the icon. Type into the field if it supports a comma-separated list of values.
  • Upload : Uploads files. Learn more.
Learn more about the icons in the Snap settings dialog.
Field / Field set Type Description
Label String

Required. Specify a unique name for the Snap. Modify this to be more appropriate, especially if more than one of the same Snaps is in the pipeline.

Default value: MCP Invoke

Example: Firecrawl MCP Server
Operation String/Expression
Required. Specify the operation to perform for the current input. The operation can be one of the following:
  • tools/call
  • resources/read
  • resources/list
The operation is provided within the sl_metadata if used with the MCP Function Generator Snap.

Default value: tools/call
Tool Name String/Expression

The name of the tool to be called. Enabled if the "Operation" is tools/call or is an expression.

Example: $function.name
Parameter String/Expression

The tool call or read resource parameters to be used for the operation.

Enabled if the Operation is a tools/call, resources/read, or is an expression.

Example: $function.json_arguments
Snap execution Dropdown list
Choose one of the three modes in which the Snap executes. Available options are:
  • Validate & Execute: Performs limited execution of the Snap and generates a data preview during pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during pipeline runtime.
  • Execute only: Performs full execution of the Snap during pipeline execution without generating preview data.
  • Disabled: Disables the Snap and all Snaps that are downstream from it.

Default value: Validate & Execute

Example: Execute only