At present, the MCP server only supports the original instruction scheduling, and does not effectively process and verify the authentication information (such as token-key) transmitted by the client or the third-party system.

In order to enhance security and expansibility, it is necessary to support the receiving and verification logic of token-key.

Comment From: kitkars

I do not think they support now. It would probably be fixed as part of ToolContext propagation.