[feature] Supports dynamic registration of prompts/tools.

[litingyes]

Description

For example, after reading data at runtime, multiple prompts or tools can be dynamically registered based on a finite-length enumeration.

Proposed Solution

No response

[HugoRCD]

Do you have any more examples, I can't see the use-case or what it might look like?

[litingyes]

Scene

I have defined a tool that calls an agent, but each time I use it, I need to pass the agent ID as a parameter. This is quite inconvenient because I have to find the agent ID every time.

Expected Usage

I will record the agent call history, temporarily store the agent ID and agent name, and then dynamically register and update the prompts, generating a new prompt similar to call_agent_xxx. This way, subsequent usage will be more convenient by utilizing the ability of the MCP server prompts to be triggered using /.

Possible Solutions

1. MCP Client support https://modelcontextprotocol.io/specification/2025-11-25/client/roots
2. The MCP server supports dynamically reading local file data to register new prompts.

[litingyes]

It's possible that something similar to Cursor doesn't yet support MCP Roots. I now have another implementation idea, but I'm not sure if it's feasible.

After the MCP server connects successfully, call a backend API to dynamically register some prompts based on the returned data (ideally, it should also support updating the prompts via notifications).