SSE Tool (MCP_SSE)

Connects an agent to a tool server (MCP server) that is already running somewhere, by its address. The agent can then use the functions (tools) this server offers.

Category: Integration (button SSE Tool at the bottom of the palette) · Deployed: yes · Tool-capable: yes (only)

Ports

Port Kind Purpose

Tool (tool_mcp)

Tool

Connect it to an Agent’s Tools port. This is the module’s only connection

Properties

Field Required Meaning

Name (name)

Marked as required

A name for this connection, so you can recognise it in the pipeline. It is a note for people only — the agent never sees it

Description (description)

No

What this server can do, in a few words. Also a note for people only — it is not sent to the agent

URL (url)

Yes

The address of the tool server, for example my-server:3000/sse. It must be an address the agent server can reach

Tool Filter (toolFilter)

No

Which functions of the server the agent may use, by their exact name. Empty → the agent may use all of them. Fewer → the agent chooses more reliably, but cannot use what is left out

The agent learns what each function does from the tool server’s own descriptions, not from the fields above.

Use cases

  • Your own tool server: an internal service offered as an MCP server and shared by several pipelines.

  • A hosted tool server from another provider, when you have its address.

  • The same server with different limits: one pipeline may use only the reading functions, another also the writing ones — set a different Tool Filter in each.

Notes

  • The URL must work from inside the agent server’s container. localhost there means the agent server itself, not your computer. On Docker Desktop, host.docker.internal reaches your computer.

  • No login can be configured. The module sends no API key or password to the server. Use it only for servers that need no login, or that are protected in another way (for example only reachable inside your network).

  • Tool Filter is your safety control. Without a filter, the agent can use every function of the server, including ones that change or delete data.

  • Fewer functions help the agent. Each function adds text the model must read on every request. A short Tool Filter makes the agent faster and its choices more reliable.

  • For a running Topic, use AI Topic instead. It finds the topic’s address for you and checks the user’s access to the topic.

  • For a ready-made tool from the Docker MCP catalog, use MCP Tool.

  • The Agent’s model must be able to use tools. Otherwise it never calls the server.