Server logo

Server

by aidemd-mcp

Maps, reads, creates, validates, and upgrades .aide project specs so agents can inspect architecture before code.

Install Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "aidemd-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@aidemd-mcp/server@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

The aidemd-mcp/server MCP server maps a project's .aide specification files and exposes their intent, research, plans, and QA context to AI agents. It uses progressive disclosure: discover the project structure first, then read detailed specs or inspect selected JavaScript and TypeScript symbols. Use it when your codebase relies on AIDE specs to preserve architectural context, validate alignment, or bootstrap the AIDE workflow.

Use cases

  • Discover project architecture from nested .aide specs
  • Read intent and research context before editing code
  • Validate spec naming, links, and project alignment
  • Bootstrap AIDE workflow files in a project
  • Inspect JavaScript or TypeScript symbol contracts

Key features

  • Progressive .aide specification discovery
  • Intent, research, plan, and QA spec management
  • AIDE naming enforcement and scaffolding
  • Spec health checks and link validation
  • JavaScript and TypeScript symbol inspection
  • AIDE initialization, upgrades, and brain status

Tools9

What Server lets your agent do. Expand a tool for its parameters.

Verified live~4.5k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

18/18 checks healthy over the last 77d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned just now via OSV.dev · @aidemd-mcp/server@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
npm downloads1.6kPackage downloads in the last 30 days.
Last commit16d agoMost recent push to the default branch.
Tools exposed9Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Server works

What aidemd-mcp/server does

The aidemd-mcp/server MCP server gives coding agents a structured way to work with .aide files stored alongside project code. These files can describe implementation intent, research, architecture plans, or QA re-alignment work. The server helps an agent inspect this context before opening implementation files, reducing the need to infer architecture from source alone.

It also supports project maintenance around the AIDE methodology. Agents can bootstrap AIDE files and workflow artifacts, check specs for structural problems, compare methodology artifacts with canonical versions, and retrieve runtime instructions for a configured brain integration.

How it works

Discovery follows two levels. A call to aide_discover without a path returns a shallow map of spec locations, types, and counts without file content. Supplying a directory opens with its ancestor chain, including inherited descriptions and alignment status, then returns summaries and warnings for the selected subtree.

After discovery, aide_read returns the selected file's content, its classified type, related specs in the same directory, and links found in the file. aide_inspect provides a narrower code-introspection step for named symbols in TypeScript and JavaScript files: it returns JSDoc, the signature, and the symbol kind without exposing the entire file.

Setup and configuration

For a Claude Code project, the documented quick start is:

Terminal
npx @aidemd-mcp/server@latest init

Initialization adds the AIDE MCP entry, creates or updates supported AIDE workflow artifacts, and can record a brain vault path with --vault-path. Existing files are not overwritten by the quick-start flow. Manual MCP configuration is also documented for Claude Code, Claude Desktop, Cursor, VS Code/Copilot, and Windsurf using an npx command that runs @aidemd-mcp/server@latest.

After editing .aide/config/brain.aide, use npx @aidemd-mcp/server@latest sync to copy its brain configuration into .mcp.json. The command preserves other MCP entries, reports malformed configuration as an error, and is idempotent when no changes are needed.

Tools and capabilities

The aidemd-mcp/server toolset includes:

  • aide_discover for project-wide maps and targeted subtree exploration.
  • aide_read for full spec content, classification, related files, and links.
  • aide_scaffold for creating intent, research, plan, todo, or paired specs while enforcing naming rules.
  • aide_validate for orphaned specs, missing specs, naming conflicts, broken links, orphaned research, and missing descriptions.
  • aide_inspect for JSDoc, signatures, and kinds of named TypeScript or JavaScript symbols.
  • aide_init for guided AIDE project bootstrapping and aide_upgrade for category-based methodology updates.
  • aide_info for startup version and brain-state checks, plus aide_brain for on-demand orientation or configuration instructions.

Limitations and notes

The server operates from the project's working directory and its filesystem artifacts; it does not replace a general code browser. Progressive disclosure means agents must make separate discovery and reading calls when they need full content. aide_upgrade writes methodology files by category after the required workflow, while MCP configuration merging remains an agent-side read, merge, and write operation. The brain tools report or return wiring instructions; they do not provide a backend themselves.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Server

aidemd-mcp/server is an MCP server that connects AI agents to a project's `.aide` specification files and JavaScript or TypeScript source structure. Its main tools discover and read specs, scaffold and validate them, inspect named symbols, initialize or upgrade AIDE artifacts, and report brain integration state.

Run `npx @aidemd-mcp/server@latest init` for the documented Claude Code quick start. It adds the AIDE MCP entry and bootstraps supported project files. Other clients can use the documented MCP configuration with `npx -y @aidemd-mcp/server@latest`.

Yes, aidemd-mcp/server works with Cursor. Add an `aide` server entry to `~/.cursor/mcp.json` with `command` set to `npx` and arguments `[-y, "@aidemd-mcp/server@latest"]`.

Call `aide_validate`, optionally with a project subdirectory path. It checks for orphaned and missing specs, naming conflicts, broken links, orphaned research files, and missing frontmatter descriptions.

Run `npx @aidemd-mcp/server@latest sync` after changing `.aide/config/brain.aide`. The command copies the declared brain configuration under the fixed `brain` key while preserving other MCP entries.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewServer AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/aidemd-mcp-server?style=directory)](https://allmcps.com/mcp/aidemd-mcp-server)
HTML Embed
<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>