"Information about Git MCP" matching MCP servers:

An MCP server that keeps raw tool output out of the context window by sandboxing and compressing results (about 98% reduction), persisting file edits, git operations, tasks and decisions in SQLite with BM25 retrieval so the agent resumes after compaction, and enforcing routing across 17 platforms via MCP and hooks. It also encourages the model to write scripts that compute answers and log only results instead of reading large data into context.

Git-backed message bus for AI coding agents — Claude Code, Cursor and Codex coordinate asynchronously, with no server

Join.cloud gives AI agents a shared workspace — real-time rooms where they message each other, collaborate on tasks, and share files via git.

Just to be clear about the final JSON: the MCP server is named herdr-inbox, and it enables Claude Code agents in herdr to ask questions asynchronously without stalling, with all open questions answered from one popup and answers routed back to the asking agent.

Provides AI assistants with real-time access to the AGNO framework documentation by enabling them to browse, search, and fetch documentation pages. This server allows users to query information about AGNO's Agents, Teams, and Workflows directly through MCP-compatible clients.

Coordinates Codex and Antigravity CLI for a structured software development workflow with workspace authorization, Git-based verification, and acceptance criteria.

A persistent memory implementation using a local knowledge graph that lets Claude remember information about users across conversations.

Enables Claude Code and Codex hosts to route work to bounded local AI subscription workers through signed-in clients, with saved workflow contracts, evidence checkpoints, reviewed model memory, video and social evidence capture, and bounded failover. Manages long-running tasks via pinned Git worktrees and an external supervisor that can swap a stopped host for another provider's client.

The AgentOps MCP server provides access to observability and tracing data for debugging complex AI agent runs. This adds crucial context about where the AI agent succeeds or fails.

A central tool aggregator that routes and orchestrates multiple fabric apps through a single MCP surface. It enables users to access a combined suite of specialized tools from various registered apps via a unified server connection.

Enables AI coding providers to run structured multi-agent workflows through MCP, including tracked tasks, document specs, handoffs, health gates, and audit evidence.

Enables coordinating Claude Code and Codex across separate Git worktrees with shared issue ownership, file reservations, messages, and explicit handoffs.

A git-backed MCP server that centrally manages AI agent skills, tools, and knowledge with role-based access, change requests, and a remote OAuth 2.1 endpoint.

An MCP server for orchestrating a fleet of CLI coding agents in isolated git worktrees. It exposes tools for spawning workers, sending instructions, reviewing diffs, and merging changes, with full terminal visibility.

Manages AI agent workflows through a state machine and Git branches, enforcing isolated phases and audit trails via SPEC, PLAN, and AGENTS files.

Enables structured multi-agent workflows by managing task claims, action logs, handoffs, and health-gated completion while keeping specifications as filesystem Markdown artifacts.

Enables AI coding providers to run structured multi-agent workflows with shared use-case and spec documents, tracked tasks, handoffs, health checks, and review/repair gates.

Provides an OAuth 2.1 authorization and login layer plus tool registration for MCP connectors, so a connector can be added to Claude clients with only a URL and password. It also shapes tool names, descriptions and input schemas for what Claude clients actually display, returning compact results and readable error messages.

Enables structured multi-agent workflows across AI coding providers by managing documents, tracked tasks, handoffs, health evidence, and MCP-owned task/action state. It supports spec creation, implementation coordination, review, triage, and health-gated completion.

Enables MCP-compatible developer environments to shrink verbose tool outputs—test logs, git diffs, directory listings, and file dumps—before they reach the context window, preserving compiler errors, failure signatures, and decisive anchors. It runs either as direct callable tools or as a transparent proxy wrapping other MCP servers such as filesystem, git, or terminal providers.