AiDD MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is AiDD MCP Server?

AiDD MCP Server is a comprehensive toolset designed for AI-driven development workflows, providing functionalities such as file system operations, code analysis, Git operations, and code execution.

How to use AiDD MCP Server?

To use AiDD MCP Server, install it via npm or pip, and configure it in your development environment. You can then access its features through the command line interface (CLI).

Key features of AiDD MCP Server?

  • File system operations (read, write, edit, move, delete)
  • Multi-language code analysis using tree-sitter
  • Git operations (status, diff, commit, branch management)
  • Code execution with safety measures
  • System information retrieval

Use cases of AiDD MCP Server?

  1. Automating file management tasks in software projects.
  2. Analyzing code structure for better understanding and refactoring.
  3. Executing code snippets in various programming languages safely.
  4. Managing version control operations efficiently.

FAQ from AiDD MCP Server?

  • Can AiDD MCP Server handle multiple programming languages?

Yes! It supports various languages including Python, JavaScript, Ruby, and more.

  • Is AiDD MCP Server free to use?

Yes! AiDD MCP Server is open-source and free for everyone.

  • How secure is AiDD MCP Server?

It includes security measures such as restricted operations to configured directories and path traversal prevention.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

13 minutes ago