Connect GitLab with Unblocked to give AI agents codebase context

GitLab gives an agent both the current implementation and the merge-request history that shaped it. Unblocked retrieves those records together, helping an agent distinguish the code that is authoritative now from the discussions that explain why it changed.

GitLab context doesn’t live alone. Unblocked links merge requests and their discussions to the code they touch, then combines them with your docs, tickets, and conversations from every other connected source. Instead of raw search results, agents and developers get one reconciled answer with GitLab sources cited.

Once connected, any MCP-compatible coding agent — Claude Code, Cursor, Windsurf, GitHub Copilot, Codex — can pull this context through a single Unblocked MCP server connection.

What you get

• Repository context — Unblocked indexes your source code and keeps it current as you push commits. The default branch is the source of truth.
• Merge request history — Every merge request and its discussion becomes searchable context. Agents can reference past MRs to understand why code works the way it does.
• Decision tracing — Unblocked traces decisions back to the merge request discussions behind them, so answers explain recent changes rather than just describing the diff.
• Cross-source synthesis — GitLab data is combined with Slack threads, Jira tickets, Confluence docs, and Sentry errors into a single knowledge graph.

Need screenshots or troubleshooting?This is a concise connection summary. Follow the complete setup guide ↗

Prerequisites

• An Unblocked account (free to start).
• A GitLab account with access to the group whose repositories you want to index. GitLab Self-Managed requires the Enterprise plan.
• An MCP-compatible coding agent (Claude Code, Cursor, Windsurf, etc.) to use the context in your editor.

Step 1: Connect GitLab to Unblocked

1. Navigate to Team Settings → Data Sources in Unblocked and select GitLab.
2. Authorize the Unblocked app via OAuth (sign in to GitLab if prompted). This lets Unblocked read your groups and repositories but doesn’t index anything yet.
3. Select the group or account whose repositories you want Unblocked to use.
4. Choose the repositories to index — Unblocked preselects repos active in the last 6 months; forks and archived repos are excluded — then click Save and Continue. Full index completes in minutes.

Step 2: Install the Unblocked MCP server

On macOS, one command auto-detects and configures your supported agents (Claude Code, Cursor, Windsurf, GitHub Copilot, Codex, VS Code):

The install script supports macOS only. On Windows or Linux, add the server manually using the configuration below, or follow the manual install guide ↗.

claude mcp add -s user --transport http unblocked https://getunblocked.com/api/mcpsse

{
  "mcpServers": {
    "unblocked": {
      "url": "https://getunblocked.com/api/mcpsse"
    }
  }
}

https://getunblocked.com/api/mcpsse

To give Claude Code, Cursor, GitHub Copilot, Codex, or another MCP-compatible AI coding agent access to GitLab context, connect GitLab to Unblocked and add the single Unblocked MCP server to your agent.

Unblocked acts as the MCP context layer for your GitLab data, searching repositories, merge requests, code history alongside your other connected sources and returning cited results through these tools:

• context_researchMulti-source research across your GitLab repositories, merge requests, docs, and messaging. Returns a synthesized answer with citations, so agents understand not just what the code does but why it changed.
• context_get_urlsFetches the full content behind GitLab merge request and file URLs your agent encounters — plus Jira, Linear, Notion, Confluence, Slack, and more.

Questions you (or your agent) can ask Unblocked about your GitLab data:

• Why was the retry logic changed in the payments service, and which MR introduced it?
• What decisions were made about the database migration approach?
• Which merge requests have touched the auth module in the last 30 days?
• What did the discussion on !1204 conclude about backward compatibility?