Build & ship · official server

GitLab for your AI agent

Give Claude Code, Cursor, Codex or your own agent GitLab through one MCP URL and one key. Your team signs in to GitLab once and the agent never holds a token. Reads run at once; anything that changes GitLab waits for your approval.

317
GitLab actions your agent gets as tools
1 URL
one endpoint for every assistant
60/min
calls per key, hard caps on top
0
GitLab credentials inside your agent

Actions

What your agent can do in GitLab

A sample of the 317 actions. Your agent sees the full list with tools/list.

Reads · run at once

  • Compare Repository Refs
  • Download Job Artifacts
  • Download Job Artifacts By Ref
  • Download Project Avatar
  • Get Commit Diff
  • Get Commit References
  • Get Commit Sequence
  • Get Commit Signature

Writes · wait for your approval

  • Add Group Member
  • Add Project Member
  • Add Spent Time
  • Approve All Group Members
  • Approve Deployment
  • Approve Group Member
  • Approve Merge Request
  • Archive Project

Official server

Also: GitLab's own MCP server

GitLab publishes its own MCP server at https://gitlab.com/api/v4/mcp. The workspace owner connects it on the Connections page with GitLab's own sign-in; Hub keeps that sign-in encrypted and passes GitLab's tools through as gitlab__<tool>. A tool GitLab marks read-only runs at once; every other one waits for your approval and runs once.

  1. Create your Vellarin account (free, no card).
  2. Open Connections → Official servers and choose GitLab. Its own sign-in page opens; approve with your account.
  3. Add Vellarin Hub to your assistant once (no code for Claude and ChatGPT; one line for Claude Code, Cursor or Codex).

Quickstart

Add Hub to your agent

  1. Create your account and connect GitLab with its normal sign-in page.
  2. Open Developers and create an agent key (you can limit it to GitLab).
  3. Add the server to your client:

Claude Code · Terminal

claude mcp add --transport http vellarin https://hub.vellarin.ai/api/hub/mcp --header "Authorization: Bearer <key>"

Cursor · ~/.cursor/mcp.json (or .cursor/mcp.json in a project)

{
  "mcpServers": {
    "vellarin": {
      "url": "https://hub.vellarin.ai/api/hub/mcp",
      "headers": {
        "Authorization": "Bearer ${env:VELLARIN_HUB_KEY}"
      }
    }
  }
}

Codex · ~/.codex/config.toml

[mcp_servers.vellarin]
url = "https://hub.vellarin.ai/api/hub/mcp"
bearer_token_env_var = "VELLARIN_HUB_KEY"

Questions

GitLab and AI agents

How do I connect GitLab to Claude Code, Cursor or Codex?

Create a free Vellarin account, connect GitLab with its normal sign-in, create an agent key on the Developers page and add the Vellarin Hub MCP server to your client with one line. Your agent then sees the GitLab actions as tools.

Can my agent change things in GitLab without asking me?

No. Read actions run at once. Any action that sends, creates, changes or deletes something in GitLab waits for the workspace owner's approval and then runs exactly once.

Does my agent get my GitLab password or token?

No. The sign-in lives on the server side. Your agent holds only a Vellarin Hub key or sign-in, which you can scope, cap per day and per month, and revoke at any moment.

What does it cost?

Hub Free includes 500 app calls a month and 1 agent key, with no card. Over the cap the answer is "upgrade or wait", never a charge. Your GitLab plan is between you and GitLab.

More behind the same address

All 104 →

GitLab is a trademark of its owner. Vellarin Hub is an independent product and is not affiliated with or endorsed by it.