briefkin

Code · 1 skill

GitLab MCP and Claude skills

Pull merge requests waiting on your review, failed pipelines on the default branch and stale issues from GitLab, and report what needs you first.

Connect GitLab to your agent (MCP)

  1. GitLab MCP server, built into GitLab at https://gitlab.com/api/v4/mcp (Self-Managed and Dedicated instances use their own host), generally available on Free, Premium and Ultimate since GitLab 19.5. In Claude Code, run claude mcp add -s user --transport http GitLab https://gitlab.com/api/v4/mcp; in Codex, codex mcp add GitLab --url https://gitlab.com/api/v4/mcp and then codex mcp login GitLab; in Cursor, add it to mcp.json with "type": "http". Clients sign in with OAuth and the mcp scope, and on GitLab.com the top-level group has to allow MCP access first. The merge_requests and ci toolsets are on by default (docs).
  2. The glab CLI. glab mr list --reviewer=@me and glab ci list --status=failed cover the same reports; set GITLAB_TOKEN (and GITLAB_HOST for your own instance) for scheduled runs.
  3. REST API with an access token. Create a personal, project or group access token with the read_api scope and store it in GITLAB_TOKEN.

read_api lets the agent read whatever the token's user can see but not comment, approve or merge; a project or group token limits that to the projects in the report.

1 GitLab skill

GitLab merge requests waiting on your review

Each weekday morning: open GitLab merge requests where you are a reviewer and have not reviewed yet, oldest first, with pipeline status and conflicts.

DevelopersWeekdays at 9:00Asks youUses GitLab.

What agents do with GitLab

GitLab's REST API v4 (https://gitlab.com/api/v4, or your own host) covers the review and CI queue. GET /merge_requests?scope=all&state=opened&reviewer_username=<you> lists merge requests waiting on you across projects, with draft, detailed_merge_status, created_at, updated_at and user_notes_count. GET /projects/:id/pipelines?ref=main&status=failed&updated_after=... finds red pipelines, and GET /projects/:id/pipelines/:pipeline_id/jobs?scope[]=failed with a job's log (/jobs/:job_id/trace) shows which job failed and why. Issues filter on labels, assignee, milestone and updated_before, and the GraphQL API at /api/graphql returns the same objects in one query.

Developers and leads schedule a morning list of merge requests waiting on their review, failed pipelines on main with the failing job's last log lines, merge requests open longer than a week, and bugs with no assignee.

about.gitlab.com

Teams that use these

Your GitLab numbers, on one board with everything else

Skills are free to use with any agent. Briefkin is where their results land: one board for every report, number and question your agents send, with a ping when something needs you.

Join the open betaBrowse all skills

Free during the open beta. No card.