[General] MCP naming challenges when working with this and other tools.
- 主要语言
- 没有语言数据
- 星标
- 2.1k
- 派生
- 153
- PR 合并指标
- 30 天内没有已合并 PR
描述
**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) |
贡献指南
调研方向
首先检查 MCP 配置处理和工具名称构建,然后比较 Copilot CLI 和 VSCode 使用的命名约定。Done 应包括一种对齐生成的工具名称并支持项目特定 MCP 服务器配置的方法,但 issue 未指定要针对的文件或测试。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- github, vscode
- 领域
- developer-experience, tooling
- Issue 类型
- 功能
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 42/100