ModelEngine-Group / ModelEngine-Group/nexent
统一 MCP 连通性检测与模型配置的交互层级
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.9k
- Forks
- 731
- Avg merge
- 19h 34m
- Merged PRs (30d)
- 172
Description
Improvement Description
当前 MCP 的连通性检测与模型配置的交互位置不统一：MCP 在添加页面就有测试按钮，而模型配置需要在添加完成后点击右上角才有测试入口，导致用户操作认知不一致。
统一配置项的测试/验证交互层级：要么都在添加表单内提供“测试连接”按钮，要么都在添加成功后的详情页/列表操作栏提供。
建议采用在添加表单内即时测试的方案，减少不必要的创建-验证-删除流程。
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the MCP add-page flow with the model-configuration add and detail/list flows described in the issue. Locate their existing test or verification entry points and choose the recommended inline form approach. Done means both configuration types expose testing at the same interaction level and users can verify before completing creation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100