Skip to main content
Glama
Janani879

DPR MCP Server

by Janani879

Related Servers

Alternatives to DPR MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to perform safe, semantic edits on Markdown and DOCX documents through a normalized model with staging, diff review, and stale-edit protection.
      13
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple AI coding agents to collaborate on the same Git repository without conflicts through isolated worktrees, file locking, automated test verification, and a serialized merge queue.
      3 npm
      6
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Provides a Model Context Protocol interface for secure, multi-agent collaboration on Git repositories, offering isolated workspaces, change requests, reviews, and approval workflows with Git as the source of truth.
      32
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables multiple AI agents to collaborate on the same git repository by coordinating work via a shared claims branch, detecting file conflicts before they happen.
      9
      23 PyPI
      PolyForm Noncommercial 1.0.0
    • F
      license
      A
      quality
      A
      maintenance
      Enables coding agents to perform workspace-confined file operations, read-only Git inspection, and structured shell commands, while requiring out-of-band human approval for mutations and external executions and maintaining an audit trail.
      14
      3
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple AI coding agents to safely collaborate in the same git working tree by managing file ownership, merging writes, and preventing snapshot races.
      6 npm
      2
      MIT

    TDQS

    B3/5.0

    Scored across 35 tools

    Disambiguation3/5

    Read_file, read_project_file, and read_change_file all fetch file content from different contexts, and approve_change/request_changes are convenience wrappers over review_change. Descriptions help, but the boundaries are easy to mix up in a set of this size.

    Naming Consistency4/5

    Snake_case imperative verb_noun naming is used consistently throughout, with no mixed casing styles. Minor deviations exist in get_/read_/ list_ patterns and the pluralized request_changes, but overall the naming is predictable.

    Tool Count2/5

    At 35 tools, the set clearly exceeds the 25+ threshold and feels heavy for an agent to navigate. Many operations are needed, but convenience wrappers and several file-read/diff variants add avoidable bulk.

    Completeness4/5

    The domain is broadly covered: workspaces and files, change creation/update/review/merge/rebase/rollback, conflict handling, and provenance. Missing project update/delete operations are a minor gap, but core workflows have no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues