Skip to content

[FEAT]: Set cooldown per MCP-Server #4817

@Samweis2111

Description

@Samweis2111

What would you like to see?

Hello,
It would be great if the cooldown could be defined per MCP-server (in the MCP-Server settings or in anythingllm_mcp_servers.json.
AFAIK MCP Cooldown is hardcoded to 30secs and can be turned off by setting MCP_NO_COOLDOWN=true in env. For tools using an internet connection or a web API with a paid service, 30 seconds is OK, and turning cooldown off could be a mistake. For other tools, like time or filesystem access, 30 seconds is too long. "Find a file and do something with it" becomes impossible. So there is no "one size fits all" value for cooldown and it would be nice if it could be defined per MCP-server - or am I missing something?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions