Code Intelligence MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CI_MCP_UTILS | No | Directly specify the path to utils.json. | |
| CI_MCP_CONFIG | No | Directly specify the path to config.json. | |
| CI_MCP_DATA_DIR | No | Specify the configuration directory containing config.json, components.json, and utils.json. | |
| CI_MCP_COMPONENTS | No | Directly specify the path to components.json. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| suggest_componentsA | USE WHEN: 用户想要创建/生成/新建/开发页面、组件或界面时。分析用户需求，从私有组件库@private-basic-components中智能推荐最合适的组件，生成包含具体实现建议的优化提示词。自动触发场景："创建页面"、"生成组件"、"新建界面"、"开发表单"、"实现功能"等所有UI开发任务。 |
| query_componentA | 根据组件名称查询详细信息，包括 props、events、slots、使用示例等。用于了解推荐组件的具体用法。 |
| suggest_utilitiesA | USE WHEN: 用户想要实现某些逻辑功能、数据处理、格式转换、工具函数等时。分析用户的逻辑需求，从工具方法库中智能推荐可以直接复用的方法，避免重复开发。自动触发场景："实现数据格式化"、"需要加密功能"、"时间处理"、"IP校验"、"数据转换"等所有逻辑开发任务。 |
| query_utilityA | 根据工具方法名称查询详细信息，包括参数、返回值、使用示例等。用于了解推荐工具方法的具体用法。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| 组件库 | 私有组件库 @private-basic-components 的所有组件列表 |
| 使用指南 | 组件建议工具的使用指南和最佳实践 |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: suggesting components vs. utilities, and querying component vs. utility details. There is no overlap or ambiguity between the four tools.
All tool names follow a consistent verb_noun pattern: suggest_components, query_component, suggest_utilities, query_utility. The naming is uniform and predictable.
With exactly 4 tools, the set is well-scoped for the server's purpose of suggesting and querying components and utilities. Each tool earns its place without redundancy.
The tool surface covers the full lifecycle for the stated domain: suggestion (discovery) and query (details) for both components and utilities. There are no obvious gaps for the intended use case.