MCP tool
Call an installed read-only remote tool once for each record
This node enriches each incoming record with a remote tool result. It connects from Semogram’s runtime to a workspace-installed MCP server, not from an outside assistant into Semogram. The discovered tool must affirm read-only behavior.
Before using it
Create or select the real resources described above in the pipeline’s project/workspace, inspect the upstream data shape and ensure your actor can perform this operation. A configuration fragment cannot create those resources. Read First pipeline for a complete graph and fixture.
Fields and bindings
| Field | Meaning |
|---|---|
Server / capabilityRefId | Installed remote MCP server capability UUID |
Tool / toolName | Discovered tool with readOnlyHint true |
arguments | Per-argument field binding or fixed literal value |
Result column / resultField | Output column; default mcp_result |
Parallel calls / concurrency | 1–8; runtime default 4 |
input / output | Upstream and enriched record-pool names |
Configure
Prepare the mcp tool node for the selected test resources. Use the operation and fields shown in this example. Show actual resource bindings, upstream/downstream ports and any write/model effects before applying the draft.Choose Server and Tool, inspect its discovered schema and bind arguments using field or literal controls. Set Result column and Parallel calls. Non-read-only tools are disabled by the inspector and rejected by execution.
Put this section under mcpTool on a full node of kind mcp-tool. It is not a standalone API or MCP request. Replace resource placeholders, and provide the full node ports/policy and graph edges.
{
"capabilityRefId": "<SERVER_CAPABILITY_UUID>",
"toolName": "get_region_owner",
"input": "orders",
"output": "enriched_orders",
"arguments": {
"region": {
"field": "region"
}
},
"resultField": "region_lookup",
"concurrency": 2
}Verify a bounded run
Inspect original rows plus region_lookup and any region_lookup_error field. The runtime retains a failed row with an error; results can be completed, partial or failed. A successful enclosing request is not proof every lookup succeeded.
Validate, save a version and run a small known fixture. Inspect the actual node result and downstream consumer, not only the graph preview.
Limits and failure behavior
The pipeline runtime supports remote http or sse servers, not stdio commands. The illustrative lookup tool must actually exist on your server. Authenticate the installation and respect remote rate limits; read-only annotation is necessary for this node.