Trae-OpenSpec MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_openspec_projectC | 基于需求描述自动创建OpenSpec项目 |
| generate_openspec_specC | 根据需求生成OpenSpec规范文件 |
| optimize_code_by_specB | 根据OpenSpec规范优化现有代码 |
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 3 tools
Each tool has a distinct purpose: creating a project, generating a spec, and optimizing code. There is no overlap or ambiguity between them.
All tool names follow a consistent snake_case pattern with verb_noun structure (create_*, generate_*, optimize_*). The naming is predictable and clear.
3 tools is well-scoped for this server's focus on OpenSpec project creation and spec-driven optimization. Each tool serves a necessary role without redundancy.
The tools cover the core workflow (create project, generate spec, optimize code). Minor gaps might include updating or deleting projects/specs, but these are not essential for the primary use case.