GitLab Claude Code

CI/CD events in your terminal.

Pipeline failures, merge request approvals, and build status changes arrive directly in Claude Code. Claude sees them too — and helps you fix the problem.

Get Started Free See how it works

claude — ~/project

Context switching kills your flow

Developers lose hours every day jumping between GitLab tabs, checking pipeline status, and missing critical merge request updates.

Time to refocus after interruption: 23 min
Daily GitLab tab switches: 20+
Deep work time lost to status checking: 70%

How it works

Three simple steps to get GitLab events in Claude Code

1 Configure: Add the pipie MCP server to your .mcp.json config file.
2 Pair: Visit our web UI to get your pairing code and connect your Claude Code instance to your GitLab projects.
3 Code: GitLab events arrive automatically in Claude Code. Focus on coding while staying informed.

Everything you need to know, when you need to know it

Comprehensive GitLab event coverage keeps your team in sync

Pipeline Failed

Get notified immediately when your CI/CD pipeline fails with error details

Pipeline Succeeded

Celebrate successful deployments and know when your code is live

MR Approved

Know instantly when your merge request gets approved by reviewers

Changes Requested

Receive feedback requests so you can address them promptly

MR Merged

Track when your contributions make it to the main branch

Build Status Changed

Stay updated on build progress from running to completed

Only see what matters

Smart Lua-based filters let you customize exactly which events you receive. Ask Claude to adjust your filters naturally: "Only show me failures on main branch" or "Just MR approvals for my code".

Branch filtering.: Only get events for specific branches like main or develop.
Author filtering.: Focus on merge requests assigned to you or from your team.
Status filtering.: Filter by pipeline status, MR state, or approval status.
Natural language.: Ask Claude to modify your filters using plain English.

gitlab-filter.lua

-- Only show critical events
if event_type == "pipeline.failed" then
  return pipeline.ref == "main"
end

-- Show MR events assigned to me
if event_type == "mr.approved" then
  return mr.assignee.username == "myusername"
end

return false

Claude doesn't just show events — it acts on them

This is what sets Claude Code apart. When events arrive, Claude can read error logs, suggest fixes, help address review feedback, and take action.

The Difference

Before Claude Code vs. After Claude Code

See how AI assistance transforms your GitLab workflow

Without Pipie

The old way

Constant context switching

Jump between GitLab tabs every 5 minutes to check for updates
Missed review requests

Frustrated teammates asking "Did you see my MR?" hours later
Pipeline anxiety

Constantly refreshing to see if your deployment succeeded
Notification overload

Email notifications buried among hundreds of other messages
Delayed responses

Hours wasted waiting for reviews that could have been done immediately

With Pipie

The better way

Stay in your flow

All updates arrive in Slack where your team already works
Instant review notifications

Get notified the moment you're assigned to review a merge request
Real-time pipeline status

Know immediately when your deployment passes, fails, or completes
Smart, filtered updates

Only see notifications relevant to you and your team's work
Faster shipping cycles

Reduced review latency means features ship hours or days faster

2 minutes to set up

Add the pipie MCP server to your Claude Code configuration

.mcp.json

{
  "servers": {
    "pipie": {
      "command": "npx",
      "args": [
        "@pipie/mcp-channel@latest"
      ]
    }
  }
}

Restart Claude Code and you're ready to receive GitLab events

Start receiving CI/CD events in Claude Code

Join developers who never miss a pipeline failure or merge request approval again

Get Started Now Using GitHub? See the GitHub version