MCP servers

Register Model Context Protocol servers in a workspace so automations can call their tools through the Orchestrator.

An MCP server offers tools over the Model Context Protocol, for example lookups in an ERP. You register it once in a workspace; automations then call its tools through the Orchestrator, which holds the server's credentials, applies time and size limits, and records every call. MCP servers are under Agentic ▸ MCP servers in the Orchestrator, and under MCP servers in the Agents menu. Server types# Type What it is Configuration Remote An external HTTP/SSE MCP server. Remote URL, Authentication (None, Bearer token or API key) Command A local subprocess that the Orchestrator starts through a command line. Command, Arguments, Environment variables Process An Orchestrator process offered as a tool. Process name Command servers run code on the Orchestrator hostCommand servers are refused unless an administrator enables them: Mcp:EnableStdioServers set to true, the allowed executables listed in Mcp:AllowedCommands, and a working directory in Mcp:StdioWorkingDirectory. Only use packages from trusted sources. A Remote server must be reachable at a public address: the Orchestrator refuses private and internal addresses and redirects. An administrator can restrict the allowed hosts further with Mcp:AllowedHosts. Add an MCP server# You need mcp_servers.create in the workspace. Open MCP servers and select Add MCP server. Choose the Server type. Under General, enter a Name (automations use it to address the server) and a Description. Keep Enabled on. Fill in the configuration for the type. For Remote, enter the Remote URL and choose the Authentication. A Bearer token or API key is stored encrypted and never shown again. Select Create MCP server. For Remote and Command servers, the Orchestrator asks the server for its tools right after it is created. A Process server offers one tool named after the process. The list shows each server's Type, Health and Description. Use Search and All types to filter. To remove a server, select ⋮ ▸ Delete. Call an MCP tool from an automation# A running job calls a tool of a workspace MCP server through the runtime API. In Python: lookup.pyPythonCopyfrom velophex import runtime answer = runtime.client().call_mcp_tool( "erp-mcp", "get_purchase_order", {"poNumber": "4500018821"}, idempotency_key="po-4500018821", ) if answer["success"]: purchase_order = answer["data"] The answer is {success, data, error, statusCode, durationMs}. Sending the same idempotency_key again returns the first answer instead of calling the server twice. See The runtime client.

Server types

Add an MCP server

Call an MCP tool from an automation