"Two agents working simultaneously" matching MCP servers:

MCP tools that let a coding agent assemble, validate and store a structured handoff document describing a change just finished, then let a receiving agent read that handoff narrowed to its own repository's required actions.

Secure localhost MCP gateway that exposes project-scoped file/Git/search tools and controlled CLI agent adapters (Codex, Claude) with fixed argv for safe Windows-native agent work.

A free, local room where multiple MCP-compatible AI coding agents collaborate on one codebase — collisions prevented, human in command.

Coordination protocol for parallel coding agents, built above Git. The MCP server exposes the full 17-tool lifecycle over stdio: register agents, publish intents with semantic scopes and declared operations, claim work, check for conflicts before code is written, publish ChangeSets, run trusted named verification checks, and record accepted work. Deterministic rules raise findings when two agents'

Enables assistants to read Forgejo repositories and manage issues and pull requests directly from the working session, using the caller's own token against any Forgejo instance.

Audits coding agents' claimed actions against the actual Git working tree, blocking completion if any claimed changes are unverified.

Enables coding agents to access approved user stories and acceptance criteria via MCP, with tools to list, retrieve, update, and check story requirements against the working tree.

MCP server that makes git rebase safe for agents by refusing unsafe operations, presenting conflicts as two intents, and verifying the branch's change against its base.

Enables building structured release evidence by comparing two Git refs and correlating commits, merged pull requests, linked issues, labels, changed files, and contributors.

Adds a live git branch status bar to the Claude interface for monitoring multiple repositories simultaneously. It provides tools for managing repository tracking and visibility through natural language commands.

An MCP server that generates release intelligence from GitHub repository data, correlating commits, pull requests, issues, and contributors between two git refs to produce structured context for release notes, changelogs, and summaries.

Exposes GitHub issue and pull-request triage capabilities to any MCP client: fetching repository context, classifying and prioritizing requests, finding duplicates, and applying labels, comments, assignments, closures, or reopenings. All writes are policy-gated, dry-run by default, and destructive actions require explicit two-step human confirmation.

Enables multi-model code review by fanning out issues to multiple LLMs simultaneously, diffing their unique insights, optionally running debate rounds, and dispatching subagents to implement fixes with git commits.

An MCP server that exposes outputty's task tracker as typed tools backed by GitHub Issues, allowing coding agents to manage tasks with two-way sync.

Analyze and compare public GitHub repository line counts (SLOC) from any MCP client. Provides per-language files, code, comment, and blank totals via the OctoCounts API, with compare_repos for side-by-side diffs of two repos or refs.

Enables an agent to run automated binary-search git bisection across a repository's mainline history using isolated git worktrees, pinpointing the commit that introduced a regression without touching the user's working copy. Each candidate is validated by a human-supplied check command, with skip/timeout handling and resumable sessions stored in SQLite.

A dynamic Azure DevOps MCP server that automatically switches authentication context based on the current working directory, enabling seamless integration with multiple Azure DevOps organizations and projects.

Provides comprehensive Git functionality to MCP clients, enabling users to manage repositories through operations like commits, diffs, and branch management via natural language. It automatically detects the current working directory and supports multi-project workflows across different local environments.

Manages parallel Git worktrees, enabling work on multiple branches simultaneously without stashing or context switching.

Enables interaction with multiple Azure DevOps organizations simultaneously, providing access to pipelines, builds, repositories, and pull requests across different organizations without switching contexts or restarting the server.