aider_check_git_logLABSCO SUMMARY
Fire-and-check, instead of waiting on the edit.
Because aider_message_prompt detaches, the calling assistant is free the moment the edit starts and can poll aider_check_progress when it wants — which is what makes several edits across several directories possible at once. The safety story rests on the whitelist: nothing outside the globs you pass is reachable, and the default is to deny. If you point it at a local OpenAI-compatible endpoint, set parallel requests to 2 or the chat and the background run will wait on each other.
What it is
A stdio server that hands coding work to aider and returns immediately. The edit runs as a detached background process; the server writes an .aider.mcp.details.json with the process ID and start time, and gives the assistant tools to check whether it is still running and what the chat history says. Basic git and file tools come along so the model can look around between checks.
What you get
aider_message_promptstartsaiderin the background with a message prompt for a given directoryaider_check_progressreads the chat history and the background process statusaider_check_last_promptreturns the original prompt of the last runaider_check_git_statusandaider_check_git_logreport working-tree state and recent commitsaider_checkout_git_branch,aider_create_git_stashandaider_git_revertswitch branches, clear the directory and undo a commit by hashaider_list_filesandaider_read_file_contentsbrowse the projectaider_setup_config_yamlandaider_read_config_yamlwrite and read.aider.conf.ymlaider_mcp_check_whitelistreports which glob paths this server is allowed to touch
Requirements
node, aider and git must all be on the shell path. Run it as npx -y mcp-aider-executor (package mcp-aider-executor, version 1.1.0) and pass at least one --whitelist glob — without one, every operation is denied. Model and endpoint come from environment variables such as AIDER_MODEL, OPENAI_API_BASE and OPENAI_API_KEY; the server deliberately cannot write API keys into the config YAML. Flags let you drop the git or file tools, or block only the git tools that rewrite history.
Setup effort
One command plus a key — npx -y mcp-aider-executor, then supply credentials
USE CASES
01
Handing off a code change and getting on with something else
Start the edit in the background, then check the chat history when you want an update.
02
Running edits across several projects at once
Launch a background run per directory, each fenced to its own whitelisted path.
03
Reviewing what the edit actually did
Read the working-tree status and recent commits, then open the files that changed.
04
Backing out a run that went wrong
Revert the commit by hash, or stash everything to clear the directory for another attempt.
14 tools
Listed in project docs. Your client may show a different list.
aider_check_git_statusaider_check_last_promptaider_check_progressaider_checkout_git_branchaider_create_git_stashaider_git_revertaider_list_filesaider_list_git_branchesaider_mcp_check_whitelistaider_message_promptaider_read_config_yamlaider_read_file_contentsaider_setup_config_yamlBEFORE YOU INSTALL
What to know first
Tools you get
14 tools named in the project's documentation.
Requires
- npx on PATH
- OPENAI_API_KEY in your environment
INSTALLATION
Connect your client
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-aider-executor": {
"command": "npx",
"args": [
"-y",
"mcp-aider-executor",
"--whitelist",
"/home/<YOUR_USERNAME>/<YOUR_PROJECT>/**",
"--whitelist",
"/local/<YOUR_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_OPENAI_API_KEY>"
}
}
}
}The two --whitelist values are glob paths of the folders the server may work in (one --whitelist per path, ending in /** to include everything below); without one, every operation is denied. Point OPENAI_API_BASE and AIDER_MODEL at your own OpenAI-compatible endpoint and model, and set OPENAI_API_KEY — any non-empty value for a local endpoint.
npx
TERMINAL
npx -y mcp-aider-executor
