Aider Executor

stdio MCP server to runaideras a detached background process with basicgittools and status checks. This allows LLMs to start code editing processes freely and check theaiderchat history for progress at a later time to allow for agentic swarm behavior.

{ "mcpServers": { "mcp-aider-executor": { "command": "npx", "args": [ "-y", "mcp-aider-executor", "--whitelist", "/home/user/my-project/", "--whitelist", "/local/my-application/" ], "env": { "AIDER_MODEL": "openai/gemma-4-E4B-it-IQ4_XS", "OPENAI_API_BASE": "http://127.0.0.1:1337/v1", "OPENAI_API_KEY": "your-key-here" } } } }

You can directly tell your LLM to use Aider by providing them with a directory to work in. For example:

Use Aider to create a simple Python hello world console application in "/home/my-project"

For extra Aider options, you should set it properly using environment variables (theenvin MCP settings .json), or ask your LLM to create the Aider YAML configuration file for you in the project directory. By default, the server comes with some basic git and file tools to allow the LLM to look around. These tools can be disabled via the options below if you'd like to use a separate MCP server to handle more advanced functions.

For security purposes, the MCP server does not have the functionality to write API keys into the configuration YAML. Useenvinstead to provide keys likeOPENAI_API_KEY. Don't tell your LLM about it.

You can add these arguments in thenpxcommand.

-h, --help Display this message --model <model> Default LLM main model override (i.e. always use this model no matter what) --edit-format <format> Main model edit format override, regardless of config or LLM inference --architect Always run in architect mode (--no-architect for never) --editor-model <model> Default secondary editor model override for architect mode --editor-edit-format <format> Editor model's edit format override --no-add-message-notes Disables the adding of aider-specific notes to message prompts --no-register-git-tools Disables registration of all git tools for this server --no-allow-git-edits Disables only the git tools which modify the repo history --no-register-file-tools Disables registration of wide file access tools for this server --whitelist <path> Only allow operations within the glob path

The environment running the MCP server must have the following tools installed and available as executable commands in the shell:

You should set the number of parallel requests to 2 if you are using the same local endpoint foraider, otherwise your chat session and the backgroundaiderprocess will be stuck waiting for each other.

You should also set theOPENAI_API_KEYenvironment variable to a non-empty value if you are using a local OpenAI-compatible endpoint becauseaiderrequires it even if you don't use an API key.

You still need theopenai/prefix when specifying model names for local endpoints inaider.

These are the list of MCP tools available for your LLM to call.

- aider_check_git_log: Checks recent commits.
- aider_check_git_status: Callsgit status --shortto check the state of the given directory.
- aider_check_last_prompt: Returns the original prompt message of the last Aider run.
- aider_check_progress: Checks the Aider chat history and background process status.
- aider_checkout_git_branch: Switches git branches, creating a new one if it doesn't exist.
- aider_create_git_stash: Stashes everything to clear the directory for Aider (git stash -u).
- aider_git_revert: Reverts changes from a git commit by its hash.
- aider_list_files: Lists all files in a given directory.
- aider_list_git_branches: Returns a list of git branches in the given directory.
- aider_mcp_check_whitelist: Checks what glob paths are whitelisted for this Aider MCP server.
- aider_message_prompt: Startsaideras a background process with a given message prompt.
- aider_read_config_yaml: Returns the full content of the .aider.conf.yml in the directory.
- aider_read_file_contents: Reads the contents of a given filepath.
- aider_setup_config_yaml: Creates the .aider.conf.yml file in the directory.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

An MCP server to help AI assistants to answer questions and generate AccelByte Extend SDK code more effectively .

Instead of direct calling MCP tools, mcpcode server transforms MCP tool calls into TypeScript programs, enabling smarter, lower-latency orchestration by LLMs.

Supercharge your Agent with Semantic Code Intelligence and save 💰 in the process!

AI-to-AI code review platform — Claude, Codex, and Gemini cross-check each other via MCP, REST API, and CLI for consensus-based results.

A code sandbox for AI assistants to safely execute arbitrary code. Requires a 302AI API key for authentication.

Agent-native developer Q&A API with MCP + A2A endpoints for citations, job pickup, and answer submission.

MCP server to dynamically load Claude Code skills into AI agents

MCP bridge that lets Claude Code delegate heavy tasks to the Antigravity CLI (agy) — purpose-built tools, model routing with fallback, session continuity, and output truncation to save Claude's context and tokens.

An MCP server for offloading AI coding tasks to Aider, enhancing development efficiency and flexibility.

Assists AI developers with requirement clarification, module design, and technical architecture.