MCP server that teaches any agent the AIDE methodology through tool descriptions and progressive disclosure tooling
Server MCP server exists for a simple reason — assistants are far more useful when they can act on Server directly instead of describing what you should do. MCP server that teaches any agent the AIDE methodology through tool descriptions and progressive disclosure tooling.
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.
Installation goes through your MCP client rather than a global install: point it at command on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Once Server is connected, these are the calls the assistant has available:
Cursor — The Cursor tool exposed by this serverWindsurf — The Windsurf tool exposed by this serveraide_discover — Scan the project for .aide spec files and return a progressive disclosure tree map showing each spec's type, location, and summaryaide_read — Read an .aide spec file with full context, returning the file content, its classified type (intent/research/plan/todo), related specs in the sameaide_scaffold — Create new .aide spec files with automatic naming convention enforcement. Handles the rename rules: intent specs are .aide by default but becomeaide_inspect — Return the JSDoc block, signature, and kind for a named function, method, class, interface, or type alias in the workspace — Tier 2 progressiveaide_validate — Run a health check on .aide spec files in the project. Detects orphaned specs, missing specs, naming conflicts (.aide and intent.aide in the sameaide_info — Boot-time precondition reporter. Returns two independent fields the orchestrator branches on separately: outdated (an array of stale AIDE artifactaide_brain — 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 brainaide_init — Bootstrap the AIDE development environment into a project using a guided one-at-a-time wizard. On the first call (no category), returns a summary ofaide_upgrade — Compare the AIDE methodology artifacts in this project against canonical versions and return a structured diff grouped by category. On the first callAmong the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Server's toolset — Cursor, Windsurf, aide_discover and 8 more — is a fair guide to whether it matches your workflow. It is maintained by aidemd-mcp; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Cursor | The Cursor tool exposed by this server. |
| Windsurf | The Windsurf tool exposed by this server. |
| aide_discover | Scan the project for .aide spec files and return a progressive disclosure tree map showing each spec's type, location, and summary. |
| aide_read | 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. |
| aide_scaffold | 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 resear |
| aide_inspect | 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 openi |
| aide_validate | 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 de |
| aide_info | 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) |
| aide_brain | 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_br |
| aide_init | Bootstrap the AIDE development environment into a project using a guided one-at-a-time wizard. On the first call (no category), returns a summary of every step with status and detected framework. On subsequent calls (wit |
| aide_upgrade | Compare the AIDE methodology artifacts in this project against canonical versions and return a structured diff grouped by category. On the first call (no category), returns a lightweight summary of every category with dr |
Or add to your project's `.mcp.json`:
```json
{
"mcpServers": {
"aide": {
"command": "npx",
"args": ["-y", "@aidemd-mcp/server@latest"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.