AiDD MCP Server logo

AiDD MCP Server

by MCP-Mirror

The AiDD MCP Server provides a comprehensive set of tools for AI-driven development workflows. It enhances AI's capability to assist in software development tasks.

View on GitHub

Last updated: N/A

What is AiDD MCP Server?

An MCP server designed to provide a suite of tools for AI-driven software development, including file system operations, code analysis, Git operations, code execution, and system information retrieval.

How to use AiDD MCP Server?

Install the server using mcp-get, pip, or uv. Configure it within your claude_desktop_config.json file. Use the aidd-cli command with the --tool and --args flags to access the various tools and their functionalities.

Key features of AiDD MCP Server

  • File system operations (read, write, edit, move, delete)

  • Directory management and traversal

  • Multi-language code analysis using tree-sitter

  • Multi-language code execution with safety measures

  • Git operations (status, diff, commit, branch management)

  • Security controls with configurable workspace boundaries

Use cases of AiDD MCP Server

  • Automated code refactoring

  • AI-assisted code generation

  • Version control management

  • System environment analysis for debugging

  • Automated file management tasks

FAQ from AiDD MCP Server

What programming languages are supported for code analysis?

The code analysis tool supports Python, JavaScript, TypeScript, Java, C++, Ruby, Go, Rust, PHP, C#, and Kotlin.

How do I configure the allowed directory?

You can configure the allowed directory in the ~/.aidd/config.json file by setting the allowed_directory property.

What is the default timeout for code execution?

The default timeout for code execution is 5 seconds.

How can I list all the available tools?

You can list all the available tools by running the command aidd-cli --list-tools.

What are the security considerations for using the code execution and shell script execution tools?

These tools execute arbitrary code/scripts on your system. Always review the code/script thoroughly, understand its purpose, never execute untrusted code/scripts, be aware of potential system impacts, and monitor execution output.