Trae Rules Generator MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYTHONPATH | No | Python path for module import resolution | . |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_existing_rulesB | 读取现有的规则文件内容 Args: rules_path: 规则文件目录路径，默认为 .trae/rules Returns: 现有规则文件的内容和结构信息 |
| generate_project_rulesB | 根据项目类型和功能特性生成新的项目规则文件 Args: project_type: 项目类型 (如: web, mobile, ai, backend, frontend 等) features: 项目功能特性列表 (如: ["authentication", "database", "api"]) language: 规则文件语言，默认为中文 Returns: 生成的规则文件内容 |
| save_rules_fileB | 保存规则文件到指定目录 Args: content: 规则文件内容 filename: 文件名，默认为 project_rules.md rules_path: 规则文件目录路径，默认为 .trae/rules Returns: 保存操作的结果信息 |
| update_existing_rulesA | 更新现有的规则文件内容 Args: file_path: 要更新的规则文件路径 updates: 更新内容的字典，支持以下键: - append_content: 要追加的内容 - replace_section: 要替换的章节 {"section_name": "new_content"} - insert_after: 在指定内容后插入 {"after": "content", "insert": "new_content"} Returns: 更新操作的结果信息 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: generating, reading, saving, and updating rules files. No overlapping functionality.
All tool names use consistent snake_case and verb_noun pattern (generate_project_rules, read_existing_rules, etc.).
Four tools are appropriate for a rules generation MCP, covering basic CRUD-like operations without being excessive.
Covers create, read, update, and save operations. Missing a delete tool, but save and update cover most workflows. Minor gap.