Open app

DocumentationWorkflowsTriggers

MCP Server node

Expose this workflow as an MCP server. Dock tools (HTTP Request, knowledge base, Outlook, …), external MCP clients like Claude Desktop or Cursor list and call them via the MCP URL. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.

7 min readUpdated

What this node does

Expose this workflow as an MCP server. Dock tools (HTTP Request, knowledge base, Outlook, …), external MCP clients like Claude Desktop or Cursor list and call them via the MCP URL.

Use MCP Server as a clearly defined step in an anymize workflow.

  • Starts a new workflow run.
  • Ends the connected path.
  • Can call approved tool nodes autonomously.

Set up the node

  1. 01Open a workflow and add MCP Server from the node catalog.
  2. 02Complete the required fields and map values from previous steps.
  3. 03Run the node with a small test record and inspect its output.
  4. 04Connect the successful output and activate the workflow after an end-to-end test.

Operations and modes

MCP Server has one focused purpose. Its available settings appear when you select the node.

Settings

FieldMeaningArea
MCP URLConfigure this value in the node panel.Protected
API keyGenerated automatically. MCP clients send the key as Authorization: Bearer <key> or header X-Anymize-Api-Key.Protected
Server name (optional)Name MCP clients see in initialize. Empty = workflow name.Standard
Instructions for clients (optional)Short hint for the MCP client (initialize.instructions). Helps the model pick tools.Standard
ToolsDocked tools, each is exposed as an MCP tool. Click a card to edit name, description, and parameters.Standard

Inputs and outputs

InputMeaningType
StandardThis trigger does not require an input.JSON
OutputMeaningType
StandardEnds this path without another output.JSON

Example and test run

MCP tool call: begin with a small, recognizable record. Inspect the output and only map fields that are present there.

Test-run example

{
  "tool": "calculator",
  "arguments": {
    "expression": "2+2"
  }
}

Access and security

Before activation, review which data enters this step and what its output contains.

Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.

Troubleshooting

  • No output: inspect the latest run and confirm that the previous node returned the expected fields.
  • Empty variable: open the previous step output and use a field name from the real test data.
  • Workflow does not start: activate it and check the trigger's test and production mode.

Related articles