Zino

Could you provide the picture referred to in the example for backtesting

> This issue is related to [#1066](https://github.com/unclecode/crawl4ai/issues/1066)此问题与 [#1066](https://github.com/unclecode/crawl4ai/issues/1066) [Fix: request /crawl with stream: true issue #1074 ](https://github.com/unclecode/crawl4ai/pull/1074#issue-3039221502) In this PR, I'd like to propose adding a feature that automatically redirects...

I plan to work on it.

Reference my approach to pass input parameters from chat requests to MCP tools, as outlined below: 1. Create an `identityToken` using the app's `input` parameters, then save and publish it....

@Nov1c444, to prevent every MCP from receiving the parameters, would it be a good idea to distinguish parameters in `inputs` using dot-separated notation (e.g., `.`)? For example, create a parameter...

> * When clicking the MCP tool settings, you could see two tabs: Parameters and Meta > * Parameters are LLM-generated, while Meta is user-defined > * You could add...

So does that mean we’ll still pass parameters via inputs, but the configuration and metadata will be handled differently? @Nov1c444

@Nov1c444 Hi , Here are my understandings and follow-up questions: 1. If we stick with passing parameters via `inputs`, after configuring the key in MCP Meta, will the Workflow fetch...

In this example, the `Field value` should be `inputs.IDkey`. right? `id_key` hasn't been defined.

Headers and _meta are two separate channels: headers work at the HTTP layer, while _meta operates at the MCP protocol layer. I’m wondering if defining something like `IDkey` in headers...