MCP Tools DirectoryAbout this integration
Git and GitHub operations — repo status, diffs, branches, PRs, issues, and Actions.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.1
- Package
- mooring-mcp
- Last compatibility test
- Not independently tested
Connect your agent
mooring-mcpPublisher README and executable manifest reviewed. The mixed authentication model is documented: local Git tools need no token, while GitHub tools require a configured token. Package and integrations were not executed or independently security-audited.
Capabilities: Inspect local Git repository status, history, diffs, blame, branches, and stashes, List and inspect GitHub pull requests, issues, and workflow runs, Create pull requests and create or update issues when authorized
Connected profiles
Additional details
io.github.seayniclabs/mooring
Source ↗ · Checked 2026-09-170.1.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17mooring-mcp
Source ↗ · Checked 2026-09-190.1.1
Source ↗ · Checked 2026-09-19Publisher documents persistent gateway operation with managed process lifecycle and crash recovery; this review did not execute that runtime.
Source ↗ · Checked 2026-09-19Local Git tools work without authentication; GitHub tools require a GitHub token supplied through the documented environment variable, so one native authentication class does not cover every tool.
Source ↗ · Checked 2026-09-19Local MCP client configuration launches the mooring console command; the existing catalog stdio connection is unchanged.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19