MCP server managing .aide spec files for intent-driven progressive disclosure of codebase architecture.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent ā or use 1-click editor setup below.
The install command below didn't complete successfully in our automated test.
npx -y commandnpm ERR! could not determine executable to run npm ERR! A complete log of this run can be found in: /home/user/.npm/_logs/2026-08-09T15_24_52_116Z-debug-0.log
This is an experimental automated check and can have false negatives ā missing environment variables, a slow cold install, etc. It doesnāt necessarily mean somethingās wrong. Last checked 1mo ago.
š” Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Server.
pathCallable MCP tool function
directoryCallable MCP tool function
typeCallable MCP tool function
intentCallable MCP tool function
researchCallable MCP tool function
bothCallable MCP tool function
MCP server that brings intent-driven development to any AI-powered IDE.
Manage .aide spec files that live next to your code ā the domain context
that architects plan from, implementors build from, and QA validates against.
Learn more at aidemd.dev.
aide_init ā wires methodology docs, pipeline commands, and this MCP server into your project in a single guided flowaide_scaffold handles the .aide / intent.aide rename rules so you never create conflicting specsaide_validate ā detects orphaned specs, missing descriptions, broken links, and naming conflicts before they cause driftaide_inspect ā returns JSDoc, signatures, and kind for named symbols without opening files, giving agents Tier 2 progressive disclosure for codeaide_upgrade ā compares your project's AIDE methodology artifacts against canonical versions and writes updates per-categoryaide_brain ā on-demand tool that returns ready-to-execute prose telling the agent which MCP tools to call and how to reach whatever brain backend is wired, without the agent knowing which backend it isThe fastest path is a single npx command that wires everything up automatically:
This command:
.mcp.json.mcp.json (vault path filled in by /aide).claude/commands/aide/.claude/agents/aide/study-playbook, brain) to .claude/skills/.aide/docs/aide-tree launcher to .aide/bin/aide-tree.mjsREADME.md (appends if not present)All operations are additive ā files that already exist are never overwritten. Safe to re-run at any time.
Pass --vault-path <path> to record your brain vault location at install time, skipping the vault-path prompt when /aide first runs.
After running, open Claude Code and run /aide ā the orchestrator will prompt for any setup the cli could not finish (IDE choice, vault path if not supplied).
Run this after editing .aide/config/brain.aide ā for example, when you update the vault path argument in mcpServerConfig.args or rename the brain in the name field:
sync reads .aide/config/brain.aide, copies mcpServerConfig verbatim into .mcp.json under the fixed brain key, and writes the name field as the server label. Every other key in mcpServers (including your aide entry and any personal MCP integrations) is left byte-identical. If a legacy obsidian key is present it is removed in the same write. The command is idempotent ā running it twice produces the same .mcp.json bytes, and the second invocation prints already in sync without touching the file. Exit code is 0 on success (including the no-change case), 1 on a missing or malformed brain.aide or invalid .mcp.json, and 2 on --help.
Example output after updating the vault path in mcpServerConfig.args:
If you use a client other than Claude Code, or prefer to configure manually, add the server entry to your client's MCP config file.
Or add to your project's .mcp.json:
[!NOTE] The Quick Start command above handles this automatically for Claude Code users.
Config file locations:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json[!NOTE] Claude Desktop does not inherit the terminal PATH. If you use nvm or Homebrew to manage Node,
npxmay not be found. Runwhich npxin your terminal to get the absolute path and replace"npx"with it in the config above.
Claude Desktop requires a full quit-and-reopen after any config change.
Add to ~/.cursor/mcp.json:
Add to .vscode/mcp.json:
[!NOTE] VS Code / Copilot uses
"servers"as the root key, not"mcpServers". Using the wrong root key causes the server to silently fail to load.
Add to ~/.windsurf/mcp.json:
Scan the project for .aide spec files and return a progressive disclosure tree map showing each spec's type, location, and summary.
Inputs:
path (string, optional): Subdirectory to drill into. When provided, the response opens with the ancestor chain ā the cascading intent lineage from root to target, each ancestor showing its description and alignment status ā followed by the detailed subtree with summaries and warnings. When omitted, returns a shallow project-wide map (locations and types only).Read an .aide spec file with full context, returning the file content, its classified type (intent/research/plan/todo), related specs in the same directory, and links found in the content.
Inputs:
path (string, required): Path to the .aide file to read.Create new .aide spec files with automatic naming convention enforcement. Handles the rename rules: intent specs are .aide by default but become intent.aide when research.aide exists in the same folder; creating a research.aide auto-renames any existing .aide to intent.aide.
Inputs:
directory (string, required): Directory where the .aide file(s) will be created.type (string, required): Type of .aide file to create. One of: intent, research, both, todo, plan.Return the JSDoc block, signature, and kind for a named function, method, class, interface, or type alias in the workspace ā Tier 2 progressive disclosure for code. Agents can understand a symbol's contract without opening the file.
Inputs:
name (string, required): Symbol name to look up.file (string, optional): Restrict search to a single file (relative to project root).Run a health check on .aide spec files in the project. Detects orphaned specs, missing specs, naming conflicts (.aide and intent.aide in the same folder), broken links, orphaned research files, and missing frontmatter descriptions.
Inputs:
path (string, optional): Subdirectory to validate. Defaults to the entire project when omitted.Boot-time precondition reporter. Returns two independent fields the orchestrator branches on separately: outdated (an array of stale AIDE artifact keys, comparing the project's versions.json against the shipped manifest), and brain (a { status, name?, hints } object reporting whether the project's brain.aide config is wired into .mcp.json). brain.status is the four-state union ok | no-brain-aide | no-mcp-entry | mcp-drift, derived by comparing .aide/config/brain.aide against .mcp.json ā no disk path validation. name is the user-declared label from brain.aide (only present on non-no-brain-aide states). hints is an array of candidate vault locations the orchestrator can surface during recovery.
Inputs:
(none)
On-demand brain entry-point tool. Call this when you need to reach the brain mid-task ā do NOT call it on every /aide boot. Boot-time brain precondition state is already reported by aide_info.brain.status; firing aide_brain at boot duplicates that work unnecessarily.
Factual signals from GitHub, npm, and our automated checks ā not a rating.
No reviews yet ā be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/aidemd-mcp-server)<a href="https://allmcps.com/mcp/aidemd-mcp-server"><img src="https://allmcps.com/api/badge/aidemd-mcp-server?style=directory" alt="Server on AllMCPs" /></a>