Model Context Protocol (MCP) server to execute aider-specific code editing operations
MCP MCP server exists for a simple reason — assistants are far more useful when they can act on MCP directly instead of describing what you should do. Model Context Protocol (MCP) server to execute aider-specific code editing operations.
An .aider.mcp.details.json file is created in the same directory with the process ID and starting datetime. The MCP server provides tools for LLM agents to check if the process is still running, and to check the .aider.chat.history.md for updates.
Once MCP is connected, these are the calls the assistant has available:
aider_check_git_log — Checks recent commitsaider_check_git_status — Calls git status --short to check the state of the given directoryaider_check_last_prompt — Returns the original prompt message of the last Aider runaider_check_progress — Checks the Aider chat history and background process statusaider_checkout_git_branch — Switches git branches, creating a new one if it doesn't existaider_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 hashaider_list_files — Lists all files in a given directoryaider_list_git_branches — Returns a list of git branches in the given directoryaider_mcp_check_whitelist — Checks what glob paths are whitelisted for this Aider MCP serveraider_message_prompt — Starts aider as a background process with a given message promptaider_read_config_yaml — Returns the full content of the .aider.conf.yml in the directorySetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
You will need 3 environment variables: AIDER_MODEL, OPENAI_API_BASE, OPENAI_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the file and storage access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP's toolset — aider_check_git_log, aider_check_git_status, aider_check_last_prompt and 11 more — is a fair guide to whether it matches your workflow. It is maintained by RailKill; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| aider_check_git_log | Checks recent commits. |
| aider_check_git_status | Calls git status --short to 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 | Starts aider as 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. |
{
"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"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| AIDER_MODEL | Configuration value read at startup. | Optional |
| OPENAI_API_BASE | Configuration value read at startup. | Optional |
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.