Skip to main content
Glama
seayniclabs

Mooring

Official
by seayniclabs

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GITHUB_TOKENNoYour GitHub personal access token. Required for all GitHub tools (gh_*). Local Git tools work without it.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription

No tools

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 12 tools

Disambiguation4/5

Clear separation between GitHub API (gh_*) and local git (repo_*) operations. While gh_issues combines list/create/update into one tool whereas PR operations are split into separate tools, the descriptions clearly distinguish their purposes with no overlapping functionality between different tools.

Naming Consistency3/5

Uses consistent prefixes (gh_ and repo_) but mixes naming patterns: gh_issues and gh_actions use nouns while PR tools use verb_noun (gh_pr_create, gh_pr_list). Local git tools follow git command names (mostly nouns) but lack verb consistency with the GitHub action-oriented names.

Tool Count5/5

Twelve tools is well-scoped for a server bridging GitHub API and local git operations. The count covers essential inspection and management tasks without bloat, with each tool earning its place in the set.

Completeness3/5

Strong read-only coverage (status, log, diff, blame, list operations) but notable gaps in write operations: no PR update/merge/close, no local git commit/push/pull/checkout, and limited Actions support (list only). The surface supports inspection workflows well but leaves agents unable to complete full git/PR lifecycle operations.

Maintenance

ActivityInactive
ResponsivenessNo issues