Skip to main content
Glama
cbuntingde

smart-coding-mcp

by cbuntingde
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to smart-coding-mcp

No user-submitted related servers found.

    Related Servers

    • lxDIG MCP

      lexCoder2
      F
      license
      B
      quality
      C
      maintenance
      MCP server that gives AI coding assistants persistent memory, structural code graph analysis, and safe multi-agent coordination, enabling them to answer architectural questions, track decisions across sessions, and coordinate safely in multi-agent workflows.
      39
      4
      -

    • myBrAIn

      lilium360
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides persistent memory and contextual awareness to language models, enabling project onboarding, recall of architectural rules, and code consistency across sessions.
      32
      MIT

    • Claude Habitat

      Ydy4HYW7ExA
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server that provides persistent project context, workflow management, and knowledge capture for AI coding agents. It enables agents to maintain structured memory across sessions by tracking project profiles, conventions, skills, and technical debt.
      7
      -

    • CodeImpact

      abhisavakar
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that indexes your codebase and gives AI assistants persistent understanding of project structure, dependencies, and history across sessions, with a self-improving multi-agent system for continuous code quality enhancement.
      11 npm
      3
      MIT
    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

    B3.4/5.0

    Scored across 14 tools

    Disambiguation3/5

    Most tools have distinct purposes, but there is overlap between analyze_path and lint_check (both analyze code) and between recall_lessons and recent_lessons (both retrieve lessons). Descriptions help differentiate, but ambiguity remains.

    Naming Consistency2/5

    Naming conventions are inconsistent, mixing verb_noun (e.g., recall_lessons), noun-only (e.g., health_check), and compound names (e.g., mark_lesson_used). No clear pattern across tools.

    Tool Count5/5

    14 tools is well within the typical 3-15 range for a focused server, covering lessons, code analysis, and configuration without feeling excessive.

    Completeness3/5

    The tool surface covers core CRUD for lessons and static analysis, but lacks a delete lesson tool and an apply fix tool, representing notable gaps for complete workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources