Fine tuned MCP modes

[kvokka]

With Roo version 3.11.15, we can create a custom mode, which might include MCP servers. Meaning that if I have a few MCP servers installed, all the tools will be sent to each mode, wasting resources.

In the latest (1.99.2) VSCode agent mode, you can choose agent mode tools, but the lack of custom modes kills all the fun.

Feature proposal draft:

# .roomodes

{
  "customModes": [
    {
      "slug": "awesome-mode",
      "name": "Awesome Mode",
      "roleDefinition": "...",
      "customInstructions": "...",
      "groups": ["mcp"],

      // new code
      "tools": {
        "mySerivce": ["bringCoffee"],
        "git": ["fetch"]
      },

      "source": "global"
    }
  ]
}

Please review this idea, and if it's acceptable and is not in the roadmap already, I can pick it up.

[carlesso]

Isn't this a duplicate of #639?
Please see if my proposal make sense please.

[kvokka]

The same idea, but apparently, there is a better solution, which is available right now. Look at the https://metamcp.com/ which is solving this very problem. Works for me

[carlesso]

The idea is interesting (although I don't get why I need to sign up for this...)
But how does this help having different mcp for different modes?

[kvokka]

Messed with the tasks, you're right. The option I provided helped to reduce the system prompt overall, but not for fine-tuning. It's the best option I've found for now with Roo/Kilo.

The thing is, it's not a big deal to implement this, but first, I need to get approval from the team to proceed and resolve the issue; otherwise, it will be for nothing. But it's been here for more than a month, as well as the issue you mentioned. I'm not ok with coding this and maintaining my fork afterwards.

I've opened a few discussions in both projects, not only on this topic, and have received 0 responses from the team, and it's been a while.