AI Adds Its Own Tools
The user says "check my calendar," but you haven't configured a calendar tool. The old way: throw an error saying "not supported." The better way: the Agent configures it itself and just asks your permission.
Capability Discovery
The Agent needs to know "what tools are available to add." This could be a tool registry or a predefined candidate list. The key is that the Agent can match a tool to the user's need.
User Authorization
AI must not silently connect to new services. It must inform the user "I want to connect to XX service" and wait for explicit consent before proceeding. This is the baseline of trust.
⚡ Instant Activation
Once configured, the new tool is immediately available without a restart. The user's current conversation continues seamlessly. This is the value of hot-loading.
Security Boundary
Which tools can be self-configured? Which require manual admin setup? For tools involving sensitive data (e.g., databases), a stricter approval process should be in place.
The traditional approach requires users to navigate to the settings page, find the MCP configuration, fill in connection parameters, and test connectivity… most users simply won't do this. Letting AI handle this process means the user only needs to say "OK" — the barrier drops from "know how to configure" to "know how to talk."