MCP Diagnostics Trae

🚀 MCP Diagnostics - Trae IDE Diagnostic Information Reading Tool

A specialized MCP (Model Context Protocol) server for Trae IDE, enabling Trae's AI Agent to obtain real-time error, warning, and hint information in the project, providing more intelligent code analysis and suggestions.

English Documentation: README_EN.md

✨ Features

• 🔍 Real-time Diagnosis: Read all diagnostic information (errors/warnings/hints) in the current workspace of Trae IDE.
• 📁 File-level Diagnosis: Obtain diagnostic information for a specified file, supporting multiple path formats.
• 📊 Statistical Summary: Quickly view diagnostic statistics (number of files, number of errors, number of warnings).
• 🤖 AI Enhancement: Enable Trae's AI Agent to understand code issues and provide more accurate repair suggestions.
• 🔌 Extended Collaboration: Obtain diagnostic information stably and efficiently through the supporting VS Code extension.
• 🎯 Intelligent Matching: Support multiple file path formats such as relative paths, file names, and absolute URIs.

🎯 Project Goals

This project is specifically designed for Trae IDE to enable Trae's AI Agent to:

• Understand real-time errors and warnings in the code.
• Provide repair suggestions based on actual problems.
• Intelligently analyze the code quality of the project.
• Assist developers in quickly locating and solving problems.

🚀 Quick Start

Step 1: Install the VS Code Extension

To allow this tool to access the diagnostic information of VS Code, you need to install the supporting VS Code extension first.

1. Open VS Code.
2. Open the command palette (Ctrl+Shift+P or Cmd+Shift+P).
3. Select “Extensions: Install from VSIX...”.
4. Find the trae-diagnostics-server-0.0.1.vsix file in the diagnostics-extension directory of this project and install it.
5. After installation, reload the VS Code window.

After successful installation, the extension will automatically run a local server in the background to provide diagnostic data.

Step 2: Clone and Build the Project

# Clone the project
git clone https://github.com/lin037/mcp-diagnostics-trae.git
cd mcp-diagnostics

# Install dependencies
npm install

# Build the project
npm run build

Step 2: Configure in Trae

1. Open Trae's MCP settings.
2. Select Add manually.
3. Paste the following configuration:

{
  "mcpServers": {
    "diagnostics": {
      "command": "npx",
      "args": ["-y", "/path/to/mcp-diagnostics"],
      "description": "Trae IDE Diagnostic Information Reading Tool"
    }
  }
}

Note: Replace /path/to/mcp-diagnostics in args with the actual path of the cloned project.

For example, after cloning the project, if it is in the E:/MCPWork/trae-diagnostics/mcp directory:

{
  "mcpServers": {
    "diagnostics": {
      "command": "npx",
      "args": [
        "-y",
        "E:/MCPWork/trae-diagnostics/mcp"
      ]
    }
  }
}

🛠️ MCP Tool List

1. getDiagnostics()

Get diagnostic information for all files in the current workspace.

Input: No parameters

{}

Output: Array of diagnostic information

[
  {
    "uri": "file:///workspace/src/index.ts",
    "diagnostics": [
      {
        "range": {
          "start": { "line": 12, "character": 5 },
          "end": { "line": 12, "character": 10 }
        },
        "severity": 1,
        "source": "typescript",
        "message": "Type 'string' is not assignable to type 'number'."
      }
    ]
  }
]

2. getDiagnosticsForPath(filePath) ⭐ Recommended

Get diagnostic information based on the file path, supporting flexible path matching.

Input:

{
  "filePath": "src/index.ts"
}

Supported path formats:

• Relative path: src/index.ts
• File name: index.ts
• File name with directory: test/TestJava.java

Output: Array of diagnostic information for the matched file

Usage examples:

• Check a TypeScript file: "filePath": "src/index.ts"
• Check a Java file: "filePath": "TestJava.java"
• Check a test file: "filePath": "test/test-errors.ts"

3. getDiagnosticsForFile(fileUri)

Get diagnostic information for a specified file (requires a complete URI).

Input:

{
  "fileUri": "file:///workspace/src/index.ts"
}

Note: Must use the complete URI format starting with file:///workspace/.

4. getDiagnosticsSummary()

Get diagnostic statistics.

Input: No parameters

{}

Output: Statistical summary

{
  "totalFiles": 4,
  "errors": 4,
  "warnings": 4
}

💻 Usage Examples

Get the project diagnostic summary

User: "Please help me check the diagnostic summary of the current project."

The AI will automatically call the getDiagnosticsSummary tool.

Get all diagnostic details

User: "Please list all errors and warnings in the current project."

The AI will call the getDiagnostics tool.

Get diagnostics for a specific file

User: "Please check the issues in the src/index.ts file."

The AI will call the getDiagnosticsForPath tool with the parameter {"filePath": "src/index.ts"}.

Supported conversation examples

• "How many errors are there in the current project?"
• "Help me find all TypeScript type errors."
• "List all warning information."
• "Check what's wrong with the TestJava.java file."
• "How is the code quality of the project?"
• "Which files need to be fixed?"

📊 Diagnostic Severity Levels

• 1 - Error ❌
• 2 - Warning ⚠️
• 3 - Info ℹ️
• 4 - Hint 💡

🔧 Technical Architecture

Trae IDE (MCP Client) ←→ MCP Server ←→ Trae IDE (DAP Interface)

1. MCP Layer: Implement the standard MCP protocol using @modelcontextprotocol/sdk.
2. Communication Layer: Communicate with Trae via stdin/stdout.
3. Diagnostic Layer: Connect to Trae IDE through the Debug Adapter Protocol.
4. Data Layer: Parse and format diagnostic information.

🛠️ Development

Run in development mode

npm run dev

Build

npm run build

Test the connection

# Start the server
npm start

# Test in another terminal
node test-file-diagnostics.js

❓ Troubleshooting

Unable to connect to Trae IDE

Solutions:

1. Ensure that Trae IDE is running.
2. Check that the project is opened in Trae.
3. Wait for the language server to complete initialization.

Return empty diagnostics

Possible reasons:

1. There are no errors or warnings in the project.
2. The language server is still analyzing.
3. The file type does not support diagnostics.

Solutions:

• Wait a few seconds and try again.
• Ensure that the file is saved.
• Check if Trae displays diagnostic information.

getDiagnosticsForFile returns an empty array

Solutions:

• Use the getDiagnosticsForPath tool (recommended).
• Ensure that the correct URI format is used: file:///workspace/file path.
• Call getDiagnostics first to view available file URIs.

Tool call fails

Check the project:

1. Whether the MCP server is started normally.
2. Whether the network connection is normal.
3. View Trae's error log.

🔮 Future Outlook

• Official Version: It is believed that Trae may develop an official version of the MCP diagnostic tool in the future.
• Community Maintenance: This project is completely developed by the author with the help of AI. Due to limited technology, future maintenance mainly relies on the community forking.
• Current Status: The current version is fully functional and sufficient for daily use.

🤝 Contribution and Maintenance

This project is developed by the author with the help of an AI assistant. Due to the author's limited technology and time, future maintenance mainly relies on the community:

• Fork Welcome: Other developers are welcome to fork this project for improvement.
• Issue Feedback: You can submit issues, but the response may not be timely.
• Pull Request: Welcome to submit PRs, and they will be reviewed as much as possible.
• Community-driven: The community is encouraged to maintain and improve the project spontaneously.

📄 License

This project is licensed under the MIT License.

🎉 Now you can let Trae's AI Agent understand the code issues in the project in real-time!