"sage active" matching MCP servers:

Enables scanning Python repos for dead code and automatically drafting a branch + PR for the safe subset (unused single-name imports) after running the repo's full test suite. All other findings are reported without modification, and a human always merges.

Enables an editor LLM to run only preconfigured lint, test, and read-only git commands, blocking arbitrary bash execution.

Enables LLM applications to interact with Google's Jules AI coding assistant to manage repositories, coding sessions, and pull requests. It allows users to programmatically create tasks, approve plans, and communicate with the assistant during active coding sessions.

Adds a live git branch status bar to the Claude footer for tracking multiple active and reference repositories. It allows users to manage repository visibility and configuration directly through natural language MCP tools.

An MCP server that retrieves GitHub Copilot usage metrics and seat assignment data across Enterprise, Organization, and Team levels. It allows users to monitor code completions, chat activity, and active user counts through integrated tools.

Enables management of co-authors for pair and mob programming sessions by automatically appending Co-authored-by trailers to git commit messages. It allows users to add, list, and configure team members as active co-authors using the git-mob CLI.

Enables read-only inspection of Git repository status and diff summaries, along with validation of OpenTofu and Ansible configurations, through a strictly limited, non-mutating toolset.

A minimal, security-focused MCP server that provides structured read/write access to exactly one local workspace, with built-in local Git checkpoints and rollback.

Enables LLM agents to search, read, and create GitHub issues and pull requests via natural language, using the GitHub API.

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{