Skip to main content
Glama
AzalHoseinian

DevInsight MCP

by AzalHoseinian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to DevInsight MCP

No user-submitted related servers found.

    Related Servers

    • github-portfolio-intelligence

      Tahas13
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides GitHub repository analysis tools for Claude, including repo summaries, commit history, issue tracking, contributor stats, and code quality assessment. Enables natural language queries about code quality, contributor activity, and repository comparisons.
      -

    • Git Helper MCP

      LetsCodeTheBrain
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to interact with git repositories by providing real-time access to repository status, branch information, commit history, and file changes. Allows users to query their git workspace through natural language commands.
      -

    • GitHub Insights MCP Server

      AhmetSOGUT
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to analyze any public GitHub repository through typed, focused tools that surface metadata, README content, file structure, detected tech stack, and Mermaid architecture diagrams. It lets users explore repo purpose, structure, and dependencies via natural language without manual browsing.
      MIT

    • mcp-git-tools

      rog0x
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to analyze local Git repositories with commit logs, diffs, blame, statistics, and branch analysis using native git commands without requiring a GitHub API.
      31 npm
      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

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of repository analysis—large files, TODOs, git log, health, stats, and tech stack. There is no functional overlap between tools.

    Naming Consistency4/5

    All names use snake_case and are descriptive, but there is a mix: two start with 'find_' (verb) while the rest start with nouns like 'git_log_', 'repo_', 'tech_'. This is a minor inconsistency.

    Tool Count5/5

    Six tools form a well-scoped set for a repository insights server. Each tool provides a distinct, valuable capability without being excessive or insufficient.

    Completeness4/5

    The set covers core areas: file analysis, TODOs, git history, overall health, stats, and tech stack. Missing features like complexity or dependency analysis are not critical gaps given the tool count.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources