Custom MCP Connections
Direnium supports custom API integrations through the Model Context Protocol (MCP). If your tool exposes an MCP endpoint, you can call its tools from workflows without writing code.
Adding a connection
- Go to Settings → Connections.
- Click Add Connection, give it a name, paste the MCP URL.
- Choose the auth type, none, Bearer token, or API key header. Direnium tests the connection.
- Direnium discovers the tools the MCP endpoint exposes.
Using a tool in a workflow
Add an MCP Call node in the builder. Pick the connection, then pick which tool to call. The node's inputs come from the tool's declared schema, so if the tool expects { email, message }, those are the inputs.
Why MCP
MCP is a protocol for exposing tools to AI systems. It lets any internal API become workflow-callable without custom integration code. It also keeps your internal services decoupled from Direnium, you control the tool implementation.