MCP Server Trigger

Expose workflows as MCP (Model Context Protocol) tools on indie.money

Written By Philippe

Last updated 3 days ago

MCP Server Trigger

✅ Supported — Custom implementation for indie.money

| Auth | Bearer Auth, Header Auth (secret saved in your Secure Vault), or none |

Compatibility

Feature	Status
Streamable HTTP transport	Supported
Tool listing (tools/list)	Supported
Tool execution (tools/call)	Supported
SSE transport	Not supported — platform constraint
Session persistence	Not supported — stateless per request

Usage

Add this trigger to an agent, then connect Tool nodes (Code Tool, HTTP Request Tool, etc.) as sub-nodes. External AI agents can then discover and call your agent's tools via the MCP protocol.

Bearer Auth and Header Auth take their token from a credential saved in your Secure Vault, in the same step as any other credential. Save it before you turn the workflow on. A call without the right token gets a 401, lists no tools, runs nothing and costs nothing. Rotate the token from your Vault page; if the credential is deleted, every call gets a 401 until you save a new one.

Was this helpful?

Still need help? Ask the team