Skip to main content
Glama
saiprashanths

Code Analysis MCP Server

by saiprashanths
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Code Analysis MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP-Python

      rhabraken
      F
      license
      Not graded
      quality
      D
      maintenance
      A server that enables interaction with PostgreSQL, MySQL, MariaDB, or SQLite databases through Claude Desktop using natural language queries.
      1
      -

    • codebase-bridge-mcp

      EDMMY
      A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server that lets a Claude chat explore your local repository and answer questions about it, returning synthesized answers with file:line references.
      3
      1
      MIT
    • Inkeep MCP Server by inkeep

      Inkeep MCP Serverofficial

      inkeep
      A
      license
      Not graded
      quality
      D
      maintenance
      A server that connects Claude to your documentation via Inkeep's API, enabling AI-powered interactions with your documentation content.
      25
      MIT

    • Claude Desktop API MCP

      mlobo2012
      F
      license
      B
      quality
      D
      maintenance
      A server that enables Claude Desktop users to access the Claude API directly, allowing them to bypass Professional Plan limitations and use advanced features like custom system prompts and conversation management.
      1
      34
      -

    • Claude Gemini MCP Integration

      cmdaltctr
      A
      license
      Not graded
      quality
      F
      maintenance
      A lightweight server that connects Claude Code with Google's Gemini AI models, allowing developers to leverage Gemini's massive context window (1M+ tokens) for code analysis without leaving their coding environment.
      233
      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

    A3.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: initialize_repository sets up the context, get_repo_info provides metadata, get_repo_structure shows the file hierarchy, and read_file accesses file contents. There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., initialize_repository, get_repo_info, get_repo_structure, read_file). The naming is uniform and predictable, using snake_case throughout with clear action descriptors.

    Tool Count4/5

    With 4 tools, the count is reasonable for a code analysis server, covering core operations like initialization, metadata retrieval, structure viewing, and file reading. However, it feels slightly thin, as advanced analysis features (e.g., linting, dependency checks) are absent, though not essential for basic functionality.

    Completeness3/5

    The toolset covers basic repository operations (initialize, info, structure, read), but there are notable gaps for a code analysis domain, such as missing tools for analyzing code quality (e.g., lint, test), searching within files, or modifying content. Agents can perform foundational tasks but may hit dead ends for deeper analysis.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources