Git Diff Patcher Bridge

Review AI code patches safely

Git Diff Patcher Bridge connects your AI to GDP through a privacy-bounded MCP endpoint. It can inspect selected repository context, diagnose patches, read local verification evidence, coordinate durable development state, classify restart requirements, compose private evidence-linked Wire drafts, and create reviewable local requests.

What you can ask

Use Git Diff Patcher Bridge to list the repositories currently open in GDP.
Example path

MCP connector

Server URL: https://mcp.methe.tech/gdp/mcp
Login: OAuth
Protocol: MCP 2025-11-25
Instructions: GDP Lane Operating Protocol v4. Protocol SHA-256: 2d19f5b2b498508951eb83a6152287fcea30057b37381b59685900b372f69796. Principle: Every lane knows every layer; not every lane acts in every layer. For repo-bound work, call first. Use when the required capability is unknown, when server or catalog identity matters, and before relying on an unfamiliar or state-changing capability. Use normal Agora for material task coordination. On multi-lane or broadcast starts, inspect existing relevant Agora context before creating a thread; prefer a user-designated or already-relevant shared thread, do not create a duplicate coordination thread merely because lanes started simultaneously, announce the intended lane and path/symbol scope, and resolve overlap before repository mutation. On your own useful finding, decision, blocker, handoff, direct question or verified completion, contribute one natural conversation_message in the relevant existing thread even when participation_needed is false; reply only to an actual conversation_message. If reports participation_needed=true after lifecycle evidence, post in that same thread instead of replying to the lifecycle signal. Use the workspace Chronicle only when cross-repository continuity or story is material; do not poll it every turn. Agora Commons is optional and non-evidentiary; participate only at a natural checkpoint, explicit invitation or returned eligibility, otherwise stay silent. Use Newsroom only for evidence-backed product milestones or explicit communication work; remains unpublished and requires human approval. After queued or local work, prefer for fresh evidence, classify that evidence, then take the smallest safe next action. When GDP reports durable_call_active or result_pending, stop status-chasing: reconcile that exact operation with a known after_* cursor through or with when an operation id is available; do not repeatedly call , , , activity feeds, or queue lists for the same pending truth. Minimize gateway round trips: use for known paths, additional_queries for related literals, and one bundle for related standalone checks. A pending durable GDP call is not completion or failure; do not submit an identical retry while it may still be active, freeze only an uncertain mutation scope, continue independent safe work, and reconcile the exact operation before dependent action. Never claim apply, test, release or production success without fresh GDP evidence. GDP Desktop retains local apply, terminal execution, commit, rollback and push authority. If your MCP host supplies no conversation metadata, then ask for the intended device/workspace and call with create_execution_context=true. Carry its execution_context on subsequent local calls; never invent conversation identity or select a different device silently. Minimize GDP gateway round trips without reducing verification quality. At task start, prefer when it is available instead of separate repository, file, check-run and queue discovery calls. When paths are known, use instead of repeated calls; use only after deterministic file-pack and direct reads are insufficient. When needs multiple literals and the capability is available, put up to four in additional_queries instead of making separate searches. After queueing a patch or checks, prefer when available instead of repeatedly listing runs, suggestions, activity and incoming queues. already runs Patch Doctor preflight internally; do not call first for a normal submission, and reserve for standalone diagnosis or repair after a preflight failure. For a new patch, include all patch-specific checks in .verification_plan; use only for standalone measurements. Put all related standalone checks or measurements in one checks array and one gateway call instead of sending one call per command. If a safe-read tool still returns a GDP gateway timeout after bounded server recovery, follow structuredContent.gateway_recovery.safe_read_retryable: retry the identical safe read once only when that field is true; otherwise do not start a parallel retry and reconcile or wait for the active durable call to settle. Never parallel-retry or automatically replay a state-changing tool after a timeout; reconcile exact durable evidence first. When structuredContent.gateway_reconciliation is present for , match its client_submission_id through or ; do not infer UI blockers and do not create a new submission id before terminal evidence. When structuredContent.gateway_recovery.durable_call_active is true and terminal is false, treat the result as a nonterminal progress receipt, not task, Lane, or Work Session completion evidence; do not stop solely because the MCP response returned, and keep reconciling that durable operation until terminal GDP evidence is observed.

Tools

Reads data70

Changes data26

Deletes or can't be undone2

Skills

None in the store listings or on the server

Screenshots

MCP connector

Server URL

https://mcp.methe.tech/gdp/mcp

OAuth

Protocol

MCP 2025-11-25

Instructions

GDP Lane Operating Protocol v4. Protocol SHA-256: 2d19f5b2b498508951eb83a6152287fcea30057b37381b59685900b372f69796. Principle: Every lane knows every layer; not every lane acts in every layer. For repo-bound work, call first. Use when the required capability is unknown, when server or catalog identity matters, and before relying on an unfamiliar or state-changing capability. Use normal Agora for material task coordination. On multi-lane or broadcast starts, inspect existing relevant Agora context before creating a thread; prefer a user-designated or already-relevant shared thread, do not create a duplicate coordination thread merely because lanes started simultaneously, announce the intended lane and path/symbol scope, and resolve overlap before repository mutation. On your own useful finding, decision, blocker, handoff, direct question or verified completion, contribute one natural conversation_message in the relevant existing thread even when participation_needed is false; reply only to an actual conversation_message. If reports participation_needed=true after lifecycle evidence, post in that same thread instead of replying to the lifecycle signal. Use the workspace Chronicle only when cross-repository continuity or story is material; do not poll it every turn. Agora Commons is optional and non-evidentiary; participate only at a natural checkpoint, explicit invitation or returned eligibility, otherwise stay silent. Use Newsroom only for evidence-backed product milestones or explicit communication work; remains unpublished and requires human approval. After queued or local work, prefer for fresh evidence, classify that evidence, then take the smallest safe next action. When GDP reports durable_call_active or result_pending, stop status-chasing: reconcile that exact operation with a known after_* cursor through or with when an operation id is available; do not repeatedly call , , , activity feeds, or queue lists for the same pending truth. Minimize gateway round trips: use for known paths, additional_queries for related literals, and one bundle for related standalone checks. A pending durable GDP call is not completion or failure; do not submit an identical retry while it may still be active, freeze only an uncertain mutation scope, continue independent safe work, and reconcile the exact operation before dependent action. Never claim apply, test, release or production success without fresh GDP evidence. GDP Desktop retains local apply, terminal execution, commit, rollback and push authority. If your MCP host supplies no conversation metadata, then ask for the intended device/workspace and call with create_execution_context=true. Carry its execution_context on subsequent local calls; never invent conversation identity or select a different device silently. Minimize GDP gateway round trips without reducing verification quality. At task start, prefer when it is available instead of separate repository, file, check-run and queue discovery calls. When paths are known, use instead of repeated calls; use only after deterministic file-pack and direct reads are insufficient. When needs multiple literals and the capability is available, put up to four in additional_queries instead of making separate searches. After queueing a patch or checks, prefer when available instead of repeatedly listing runs, suggestions, activity and incoming queues. already runs Patch Doctor preflight internally; do not call first for a normal submission, and reserve for standalone diagnosis or repair after a preflight failure. For a new patch, include all patch-specific checks in .verification_plan; use only for standalone measurements. Put all related standalone checks or measurements in one checks array and one gateway call instead of sending one call per command. If a safe-read tool still returns a GDP gateway timeout after bounded server recovery, follow structuredContent.gateway_recovery.safe_read_retryable: retry the identical safe read once only when that field is true; otherwise do not start a parallel retry and reconcile or wait for the active durable call to settle. Never parallel-retry or automatically replay a state-changing tool after a timeout; reconcile exact durable evidence first. When structuredContent.gateway_reconciliation is present for , match its client_submission_id through or ; do not infer UI blockers and do not create a new submission id before terminal evidence. When structuredContent.gateway_recovery.durable_call_active is true and terminal is false, treat the result as a nonterminal progress receipt, not task, Lane, or Work Session completion evidence; do not stop solely because the MCP response returned, and keep reconciling that durable operation until terminal GDP evidence is observed.

Tools