How is this different from connecting GitLab MCP directly?

Connected directly, an agent sees every tool the server exposes and holds the credential itself. Through TrustGate you choose which tools each agent gets, and every call is logged against the agent that made it.

What if the GitLab MCP API changes?

We track the GitLab MCP schema, so the tool catalogue stays current. Tools you have already allowed keep working, and anything new stays denied until you enable it.

Can I give different agents different GitLab tools?

Yes. Access is set per agent: one can get a handful of read tools, another the full set. You grant the whole MCP or single tools within it.

Where can I see what my agents did in GitLab?

Every call is logged against the agent that made it, with the tool it used. Activity can be sent on to your own monitoring.

Do I need to run the GitLab MCP server myself?

No. TrustGate connects to the GitLab MCP server and sits in front of it. Your agent only talks to your TrustGate URL, never to GitLab directly.

Connect GitLab MCP to your AI agents, securely.

Q: Is GitLab MCP secure?

The server itself exposes 46 tools, and some of them can write to your GitLab account. Behind TrustGate an agent only sees the tools you allow, requests and responses are inspected, and every call is logged. Anything outside the allowlist is denied before it reaches GitLab.

One secured endpoint for every GitLab call your AI agents make, scoped per user, inspected, and logged.

Get started for free

Get a demo

Try GitLab MCP now

What your agents can ask once GitLab MCP is connected.

“List my open merge requests in this project”
“Show the failed jobs in the latest pipeline”
“Create a work item for this bug”

“Read the file at app/models from the default branch”
“Which critical vulnerabilities are open?”
“Leave review comments on this merge request”

Select the tools your AI agents can call

46 tools from the GitLab MCP schema.

Showing 46 tools

get_mcp_server_versionreadReturns the current version of the GitLab MCP server.
get_projectreadReturns metadata for a single GitLab project: numeric ID, full path, default branch, visibility, and web URL.
list_project_membersreadLists the members of a GitLab project with their role and access level.
fork_repositorywriteForks a GitLab project into a namespace.
list_projectsreadLists the projects you can access, or every project in a group and its subgroups.
list_groupsreadLists groups and subgroups, to navigate the group hierarchy and discover group IDs and paths.
add_commitwriteAdds a commit with one or more file actions to a branch in a single call.
add_branchwriteAdds a branch to a GitLab project from a source ref.
list_branchesreadLists the branches of a GitLab project, optionally filtered by name.
get_repository_filereadRetrieves the contents of a single file from a repository at a specific ref.
list_repository_treereadLists the files and directories in a GitLab repository at a given path and ref.
get_commitreadRetrieves a single commit's metadata, and optionally its diff or notes.
list_commitsreadLists the commits of a GitLab project, optionally filtered by ref, author, path, or date.
list_releasesreadLists releases in a GitLab project, most recently released first.
list_tagsreadLists tags in a GitLab project, most recently updated first.
list_wiki_pagesreadLists the wiki pages in a GitLab project or group.
save_merge_requestwriteCreates or updates a merge request in a GitLab project.
get_merge_requestreadRetrieves a merge request and, optionally, its diffs, commits, notes, pipelines, discussions, approvals, or conflicts.
list_merge_requestsreadLists or searches merge requests in a GitLab project or group.
save_merge_request_reviewwriteWrites merge request review artifacts: notes, diff comments, discussion resolution, review submission, approval or unapproval.
accept_merge_requesthigh riskMerges a merge request, or schedules it to merge automatically.
save_notewriteAdds a comment to a GitLab merge request or work item, or replies to an existing discussion thread.
get_work_itemreadRetrieves a single work item with its type, dates, assignees, labels, milestone, and parent.
save_work_itemwriteCreates or updates a GitLab work item, such as an issue, task, or epic.
link_work_itemswriteLinks a work item to one or more other work items with a relationship type.
get_saved_view_work_itemsreadRetrieves a saved view and its list of work items from a namespace.
list_work_itemsreadLists or searches work items such as issues, incidents, tasks and epics in a group or project.
get_work_item_typesreadLists the work item types available in a group or project, including custom types and their enabled widgets.
get_pipelinereadRetrieves a pipeline, and optionally its jobs, downstream pipelines, bridge jobs, or artifacts.
list_pipelinesreadLists pipelines in a GitLab project, with optional filters.
save_pipelinehigh riskRuns, retries, cancels, or renames a CI/CD pipeline in a GitLab project.
get_jobreadGets a CI/CD job's metadata, and optionally its trace log or the artifacts it produced.
get_artifact_filereadReads a file from inside the artifacts archive of a CI/CD job as text.
list_vulnerabilitiesreadLists security vulnerabilities in a GitLab project, with optional filters and cursor pagination.
get_vulnerabilityreadReturns comprehensive details for a single vulnerability, including title, state, description, severity, and identifiers.
save_vulnerabilitywritePerforms write operations on a vulnerability: dismiss, confirm, revert to detected, update severity, or create an issue.
attach_scan_profilewriteAttaches a security scan profile to the given projects, or to all projects under the given groups. Ultimate only.
list_duo_agents_and_flowsreadLists the GitLab Duo agents and flows enabled in a project.
start_duo_sessionwriteStarts an asynchronous GitLab Duo Agent Platform session to accomplish a goal in a project.
list_duo_sessionsreadLists your GitLab Duo Agent Platform sessions, excluding Duo Chat sessions.
get_duo_sessionreadChecks the status of a GitLab Duo Agent Platform session.
send_duo_session_inputwriteAnswers a GitLab Duo Agent Platform session that is waiting for input.
get_userreadGets a single GitLab user, by username, numeric ID, or the authenticated account.
searchreadFull-text search across GitLab resource types.
search_labelsreadSearch labels available in a project or group.
semantic_searchreadSearches a project's code semantically with natural language, replacing semantic_code_search (still accepted as an alias). Requires GitLab Duo.

What GitLab MCP exposes

GitLab MCP groups its 46 tools into 11 categories, each with a suggested starting policy.

Category	Covers	Access	Suggested policy
Repository	Commits, branches, files, tree, releases and tags	Read / Write	Scope projects; audit commits and branch creation
Merge Requests	Merge request details, listing, creation, review and merge	Read / Write	Require approval for merges
CI/CD	Pipelines, jobs, logs and artifact files	Read / Write	Restrict pipeline execution
Duo	GitLab Duo agents, flows and agent sessions	Read / Write	Approve agent session execution
Work Items	Issues, tasks, epics, links and saved views	Read / Write	Audit changes
Projects	Project metadata, members and forking	Read / Write	Limit organization access
Security	Vulnerability listing, detail and state changes	Read / Write	Limit access to security findings
Search	Full-text search, label search and semantic code search	Read	Limit access to intended projects
Notes	Comments on merge requests and work items	Read / Write	Audit publishing
Users	User lookup by username or ID	Read	Limit organization access
Server	MCP server version	Read	Allow version checks