Skip to main content
Glama
Charan-Sharan

dpr-mcp

by Charan-Sharan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to dpr-mcp

No user-submitted related servers found.

    Related Servers

    • GitHub MCP Server

      jungchihoon
      A
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol server that provides 29 Git operations and advanced workflows, enabling AI assistants and developers to safely manage version control.
      30
      358 npm
      1
      ISC

    • DPR MCP Server

      Janani879
      A
      license
      B
      quality
      C
      maintenance
      Enables safe, human-in-the-loop AI document collaboration by letting agents create isolated workspaces, edit tracked files, open reviewable Change Requests, and get human approval before merging, with Git-backed conflict detection and resolution.
      35
      MIT

    • git-mcp-server

      cyanheads
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that enables Large Language Models to interact with Git repositories through a robust API, supporting operations like repository initialization, cloning, file staging, committing, and branch management.
      28
      3,381 npm
      240
      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

    B3/5.0

    Scored across 32 tools

    Disambiguation5/5

    Every tool targets a distinct resource-action pair: projects, files, workspaces, changes, and conflicts. Even the convenience wrappers (approve_change, request_changes) are clearly labeled and do not overlap with the core review_change. The boundaries between get_history, get_revision, and get_diff are evident from their descriptions.

    Naming Consistency5/5

    All 32 tool names follow a strict verb_noun pattern in lowercase snake_case (e.g., create_project, list_workspaces, rebase_change). Verbs are consistently imperative and specific, making the toolset predictable and easy to navigate.

    Tool Count3/5

    32 tools is heavy compared to typical server scopes, but the domain (Git-backed project management with workspaces, change lifecycle, and conflict resolution) is broad enough to justify a larger surface. Still, it leans toward the upper limit, and some consolidation could be possible without losing clarity.

    Completeness4/5

    The toolset covers the full lifecycle: project creation, file manipulation, workspace management, change creation/review/merge/rollback, and conflict handling. Minor gaps exist (e.g., no delete_project or rename operations), but the core workflow is complete and agents can accomplish all major tasks without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources