[General] MCP naming challenges when working with this and other tools.

**Mood:** 😊
**Category:** General

I love this tool! But I have one serious problem with it's MCP Config. My team uses multiple tools including Copilot CLI and VSCode. Both of those tools construct MCP tool names as "mcp__" and my team has codified 10's of skills that directly reference these tool names.

Github Copilot consturcts as "-" (a hyphen instead of an underscore) and so there is no way to get the tool names to line up.

It would also be really nice to allow MCP servers to be specfiic to specific projects (instead of user config) both so it could be automatic on a large team and so it can vary by project. We have one game that exposes an MCP server so that only makese sense in the context of that repo/project.

---
| Field | Value |
| --- | --- |
| App version | 1.0.9 |
| OS | Windows 10.0.26200 |
| Theme | Notionish |
| Path | /chat |
| Tenure | Day 6 (Week 1) |

Commencez par examiner la gestion de la configuration MCP et la construction des noms d’outils, puis comparez les conventions de nommage utilisées par Copilot CLI et VSCode. Done devrait inclure un moyen d’aligner les noms d’outils générés et de prendre en charge la configuration de serveurs MCP propre au projet, mais l’issue n’indique aucun fichier ni test à cibler.

Rédigé par le modèle d'indexation à partir du texte de l'issue.