
Mooring
io.github.seayniclabsPublished by GitHub account seayniclabsv0.1.1Updated Oct 25, 2026
Git and GitHub operations — repo status, diffs, branches, PRs, issues, and Actions.
Overview
Mooring is a local MCP server that gives an AI assistant structured access to local Git repositories and the GitHub API for status, diffs, branches, PRs, issues
- What you can do
- Inspect local repositories: status, commit log, diffs, blame, branches and stash operations, with paths validated against the repository root and refs checked before use. Work with GitHub pull requests: list, view details with reviews, comments and check runs, and create new PRs. Manage GitHub issues: list, create or update them. Review GitHub Actions workflow runs by workflow and status. Check server version and health.
- When to use it
- Useful when an assistant should help with day-to-day Git work in local repositories and with GitHub pull requests, issues and CI runs without switching tools. Best for developers who want read-heavy repository inspection plus a few write actions such as creating PRs and updating issues.
- Requirements
- Runs as a local Python process installed from PyPI (pip or pipx) and started with the mooring command. A GITHUB_TOKEN environment variable is required for all GitHub tools; local Git tools work without it. Desktop client configuration only.
Installation
In SourceWeft
- Open Mooring in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.