GitLab MCP Server

Search Merge Requests

search_merge_requests

Read-onlyIdempotent

Search GitLab merge requests by username or project path, filter by state, sort, and paginate results; use a project path for text searches.

Instructions

Search merge requests by username (supports "username", "author:username", "assignee:username") or search within a specific project. Note: GitLab does not support global text search for MRs - use projectPath for text searches.

Input Schema

Name	Required	Description	Default
`sort`	No	Sort order (e.g., UPDATED_DESC, CREATED_DESC, CREATED_ASC). Defaults to UPDATED_DESC for recency.
`after`	No	Pagination cursor. To fetch the next page, pass the previous response pageInfo.endCursor here and repeat until pageInfo.hasNextPage is false. Paginating this way is the reliable path to complete results and accurate totals.
`first`	No	Number of merge requests to retrieve
`state`	No	Filter by merge request state (opened, closed, merged, all)	all
`fetchAll`	No	Fetch multiple pages in one call, up to "first" items total (max 100) — NOT exhaustive. For complete results or accurate counts, leave this false and paginate via after (pageInfo.endCursor).
`searchTerm`	Yes	Username (e.g., "cdhanlon", "author:username", "assignee:username") or text when projectPath provided
`projectPath`	No	Project path (e.g., "group/project"). Required for text searches, optional for username searches.
`userCredentials`	No	Your GitLab credentials (optional — falls back to the configured env token if not provided)

Output Schema

Name	Required	Description	Default
`nodes`	Yes
`hasMore`	No
`pageInfo`	Yes
`totalFetched`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv4.0.0Nov 2, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / userCredentials / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "accessToken": {
-        "minLength": 1,
-        "type": "string"
-      },
-      "gitlabUrl": {
-        "format": "uri",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "accessToken": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "gitlabUrl": {
+        "format": "uri",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "hasMore": {
+      "type": "boolean"
+    },
+    "nodes": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "iid": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "webUrl": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "iid",
+          "title",
+          "webUrl"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pageInfo": {
+      "additionalProperties": {},
+      "properties": {
+        "endCursor": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "hasNextPage": {
+          "type": "boolean"
+        },
+        "hasPreviousPage": {
+          "type": "boolean"
+        },
+        "startCursor": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "hasNextPage",
+        "endCursor"
+      ],
+      "type": "object"
+    },
+    "totalFetched": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "nodes",
+    "pageInfo"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv2.2.4Jul 24, 2026

changedInput schema / properties / after / description

Previous value: -"Cursor for pagination"New value: +"Pagination cursor. To fetch the next page, pass the previous response pageInfo.endCursor here and repeat until pageInfo.hasNextPage is false. Paginating this way is the reliable path to complete results and accurate totals."

changedInput schema / properties / fetchAll / description

Previous value: -"Fetch all pages up to 100 results"New value: +"Fetch multiple pages in one call, up to \"first\" items total (max 100) — NOT exhaustive. For complete results or accurate counts, leave this false and paginate via after (pageInfo.endCursor)."

Changed3 schema fields changedv1.15.0May 10, 2026

addedInput schema / properties / fetchAll

Added value: +{
+  "default": false,
+  "description": "Fetch all pages up to 100 results",
+  "type": "boolean"
+}

addedInput schema / properties / sort

Added value: +{
+  "description": "Sort order (e.g., UPDATED_DESC, CREATED_DESC, CREATED_ASC). Defaults to UPDATED_DESC for recency.",
+  "type": "string"
+}

changedInput schema / properties / userCredentials / description

Previous value: -"Your GitLab credentials (optional - uses shared token if not provided)"New value: +"Your GitLab credentials (optional — falls back to the configured env token if not provided)"

First observedv1.7.3Mar 7, 2026

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds the useful platform limitation about no global text search, but that constraint is largely mirrored in the schema's searchTerm and projectPath descriptions, and nothing is said about result volume or pagination behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero filler, with the primary search modes stated first and the important limitation immediately after. Nothing needs trimming.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema, full parameter documentation, and safety annotations, the description only needs to convey search semantics and platform limits — both are present. The remaining gap is routing: in a sibling set containing get_merge_requests, get_user_merge_requests, and search_gitlab, it does not say which to prefer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all eight parameters are documented in the schema itself, including sort, paging via after/first, state, and the searchTerm/projectPath relationship. The description repeats the username formats without adding syntax or behavior beyond what the schema already states; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource plus the two operating modes: username search (with author:/assignee: prefixes) or search scoped to a project. It does not, however, distinguish itself from close siblings such as get_merge_requests, get_user_merge_requests, or search_gitlab, so an agent must infer the difference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states an explicit usage constraint — GitLab does not support global text search for MRs, so text searches must supply projectPath. That is a real when/when-not with a prescribed remedy, but no sibling alternative is named for cases like listing MRs without a search term.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server