Skip to main content
Glama
sapientpants

DeepSource MCP Server

by sapientpants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to DeepSource MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP DeepWiki Server

      LoganZechella
      -
      license
      B
      quality
      Not graded
      maintenance
      A Model Context Protocol server that enables AI assistants to fetch and understand GitHub repository documentation on-demand from DeepWiki during conversations.
      3
      -
    • CodeAlive MCP by CodeAlive-AI

      CodeAlive MCPofficial

      CodeAlive-AI
      A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol server that enhances AI agents by providing deep semantic understanding of codebases, enabling more intelligent interactions through advanced code search and contextual awareness.
      90
      MIT

    • MCP Dev Standards

      han0420
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that provides development standards and best practices context to AI coding assistants, ensuring generated code adheres to team/project conventions.
      3
      14 npm
      1
      MIT

    • Codebase MCP Server

      cmaujean
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that analyzes application codebases with real-time file watching, providing AI assistants like Claude with deep insights into project structure, code patterns, and architecture.
      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 10 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (projects vs runs vs issues vs metrics vs security). However, project_issues and recent_run_issues both deal with issues and could cause initial confusion, though descriptions clarify the difference.

    Naming Consistency4/5

    Tool names follow a predictable pattern: query tools are named after the resource (noun or noun phrase, e.g., projects, runs, quality_metrics) and mutation tools use verb_resource (e.g., update_metric_setting). This is consistent and readable.

    Tool Count5/5

    10 tools is well-scoped for a code analysis server, covering core areas (projects, runs, issues, metrics, compliance, dependencies) without being overwhelming or too sparse.

    Completeness3/5

    The tool set covers most essential operations (list, get, update for key resources) but lacks branch listing (needed for recent_run_issues) and triggering analysis runs, which are notable gaps for a comprehensive interface.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources