Summary
No new token: it borrows the glab login you already did.
That removes the usual step of minting a personal access token and deciding its scopes. glab_raw and glab_api are the escape hatches — anything the typed wrappers miss is still one call away, which matters on a self-managed GitLab with unusual features.
What it is
A Swift server that wraps the GitLab CLI. It uses the credentials glab already holds on your machine, parses JSON output where glab produces it, and falls back to plain text where it does not.
What you get
- glab_mr — merge requests: list, create, view, merge, approve
- glab_issue — issues: list, create, view, close, update
- glab_ci — pipelines: view, list, run, retry
- glab_repo — repositories: clone, fork, view, archive
- glab_api — direct GitLab API access for anything the wrappers do not cover
- glab_auth and glab_version
- glab_raw — any glab command, verbatim
- Four guided prompts: my-mrs, create-mr, daily-standup and review-pipeline
Requirements
macOS with Swift 5.9 or later, and the glab CLI installed and already logged in — the server uses that existing authentication rather than asking for a token. Build with Swift Package Manager and point the client at the built binary; the config needs a PATH entry so glab is findable.