MCP Workflow Bindings

[viktormarinho]

Workflow Bindings

• MCPs can implement a workflow binding that comes with two things:
  • CRUD Workflow tooling as needed, but requires LIST_WORKFLOWS and GET_WORKFLOW_BY_ID
  • Some way for the MCP to say, on any tool (maybe on the tool response, or inside the tool with a ctx.HEY_DECO_I_STARTED_A_WORKFLOW_WITH_ID_123) that they started a workflow
  • This ensures that our workflow UI can be compatible with both CF Workflows (that should be behind this binding as well) and workflows of third parties as well, so we now support background tool calls, etc. Example: Openai Deep research API.

[viktormarinho]

I see our workflows UI having a select where you choose which MCP you want to see the workflows

[viktormarinho]

We can maybe also solve streaming tool calls this way.

I believe we should support subscribing to a Workflow in some way, and that supports streaming as well!

So, we can use this to make our LLM calls tool calls as well. The way that i see this is:

• frontend chat ui SUBSCRIBES to a workflow with thread ID. (kinda like a "topic" in some distributed systems things)
  the only job of this ui is to stream in anything going into that thread workflow topic

• the tool call for generating something is kinda fire and forget, we just send the message and this GENERATE_WITH_LLM tool call will then stream into that workflow topic the result

• this enables a lot of things, and could even be the default for all of our tool calls if you wanna go that way

[lucis]

This is a very important feature.

In the age of AI, a lot of computing tasks will

1. Take time
2. Require coordination of steps to complete

Workflows is an appropriate abstraction to deal with those requirements.

Some examples for us to design the solution:

• GPT Imagen generating a new image (~2min)
• Deep Research job (~10min)
• Landing Page creation workflow (~1min)
• Daily summarizer of emails (~1min)

For all of those three I want:

• A system wide notification when the workflow is finished.
• A dynamic loading UI that will change according to each step.

[lucis]

Just like all bindings, Workflows will have a OS-level integration that multiple agents and apps can use.

MCPs that want to leverage this functionality should implement the Workflow binding a call the designated tool to register a new workflow.