Skip to main content
Glama
aidemd-mcp

aidemd-mcp/server

by aidemd-mcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to aidemd-mcp/server

  • Obsidian

    clavia-labs
    A
    license
    Not graded
    quality
    Not graded
    maintenance
    This is a connector to allow Claude Desktop (or any MCP client) to read and search any directory containing Markdown notes (such as an Obsidian vault).
    685 npm
    1,352
    AGPL 3.0

Related Servers

  • arch-viewer

    axumquant
    A
    license
    Not graded
    quality
    D
    maintenance
    Provides AI-powered architecture analysis and visualization of codebases, exposing 17 MCP tools for querying components, dependencies, and generating interactive diagrams.
    0
    1
    MIT

  • Foundry MCP

    foundry-works
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables spec-driven development workflows with AI assistants, providing tools for managing specification lifecycles, task dependencies, code navigation, testing, and automated reviews through a unified CLI and MCP interface.
    4
    MIT

  • Grafyx

    bilal07karadeniz
    A
    license
    A
    quality
    A
    maintenance
    Enables AI coding assistants to understand codebase architecture in real time by parsing source code into a relationship graph and exposing call chains, dependencies, class hierarchies, and conventions via MCP tools.
    14
    4
    MIT
  • NEAT MCP Server by NEAT-Technologies

    NEAT MCP Serverofficial

    NEAT-Technologies
    A
    license
    Not graded
    quality
    A
    maintenance
    Provides AI agents with a live architecture model of a codebase, enabling queries for root cause analysis, blast radius, and dependency traversal through MCP tools.
    156 npm
    18
    Apache 2.0
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored across 9 tools

Disambiguation3/5

Most tools have distinct purposes (discover, read, scaffold, validate, upgrade, info, brain, init, inspect), but 'aide_info' and 'aide_brain' both deal with brain state and could be confused—one is boot-time, the other mid-task. 'aide_upgrade' and 'aide_init' overlap in writing infrastructure files but target different phases.

Naming Consistency4/5

All tools use the consistent prefix 'aide_' followed by a verb, creating a clear pattern. However, verbs vary between nouns (info, brain) and actions (discover, read, scaffold, validate, upgrade, init, inspect), and 'aide_info' and 'aide_brain' are not verb-like, breaking the otherwise clean verb_noun pattern.

Tool Count4/5

9 tools is within a reasonable range for a methodology server, covering the full lifecycle from discovery to validation to upgrade. It's slightly above the minimal 3-15 sweet spot but justified by the domain's complexity, though some simpler servers might not need all these tools.

Completeness5/5

The tool surface covers the complete spec workflow: discover, read, scaffold, validate, and also includes lifecycle management (init, upgrade, info) and an on-demand brain entry point. There are no obvious dead ends—each tool either feeds into another or handles a distinct lifecycle stage, ensuring agents can execute full workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources