# Approve Merge Request — GitLab

> Approve a merge request as the authenticated user, or withdraw an earlier approval by setting Action to unapprove. Call Get Merge Request first to check the merge request is actually ready — its readiness rollup reports the pipeline…

- Key: `gitlab-approve-merge-request`
- Type: Action (Write)
- Version: 0.0.1
- App: GitLab (`gitlab`) — https://pipedream.com/apps/gitlab.md
- This page (HTML): https://pipedream.com/apps/gitlab/actions/approve-merge-request
- Hints: open-world
- Source: https://github.com/PipedreamHQ/pipedream/blob/master/components/gitlab/actions/approve-merge-request/approve-merge-request.mjs

## Description

Approve a merge request as the authenticated user, or withdraw an earlier approval by setting **Action** to `unapprove`. Call **Get Merge Request** first to check the merge request is actually ready — its `readiness` rollup reports the pipeline status, conflicts and how many approvals are still required — and **Get Merge Request Diffs** to read the changes being approved. Two things commonly go wrong: GitLab **refuses to let you approve your own merge request**, and a project may require approval from a specific approval rule that the authenticated user does not satisfy; both surface as a `401`. To approve as part of leaving review feedback in one step, use **Create Merge Request Review** with its **Action** set to `approve` instead. Optionally pass **SHA** to make the approval conditional on the merge request's head commit, so it fails rather than silently approving work that was pushed after you read the diff. [See the documentation](https://docs.gitlab.com/api/merge_request_approvals/#approve-merge-request)

## Props

| Prop | Type | Required | Description |
|---|---|---|---|
| `projectId` | `string` | Yes | The project, given either as its path — group/project or group/subgroup/project, e.g. backend/payments — or as its numeric project ID. The path is what appears in the project URL and is usually what a user will name, so prefer it. A pasted GitLab URL also works. Use List Projects to find the path if you only know part of the name. |
| `mergeRequestIid` | `integer` | Yes | The merge request's internal ID — the !N shown in the GitLab UI and the number at the end of the merge request URL. This is not the id field, which is a much larger instance-wide number; passing id here returns a 404. Use List Merge Requests or Search Merge Requests to resolve the IID from a title, branch or author. |
| `action` | `string` | No | approve (the default) records an approval; unapprove removes one the authenticated user gave earlier. There is no REST equivalent of GitLab's Request changes reviewer state — to block a merge request, unapprove it and explain why with Create Merge Request Comment. |
| `sha` | `string` | No | Optional head commit SHA to approve. When set, GitLab rejects the approval if the merge request's head has moved on — use the diff_refs.head_sha returned by Get Merge Request to be sure you are approving the code you read. Ignored when Action is unapprove. |

## Run it

**MCP**

```ts
import { Client } from "@modelcontextprotocol/sdk/client/index.js"
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js"
import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const accessToken = await pd.rawAccessToken

const transport = new StreamableHTTPClientTransport(
  new URL("https://remote.mcp.pipedream.net/v3"),
  {
    requestInit: {
      headers: {
        Authorization: `Bearer ${accessToken}`,
        "x-pd-project-id": process.env.PIPEDREAM_PROJECT_ID!,
        "x-pd-environment": "production",
        "x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
        "x-pd-app-slug": "gitlab",
      },
    },
  },
)

const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)

const { tools } = await mcp.listTools()

// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
  name: "gitlab-approve-merge-request",
  arguments: {
    projectId: "Project",
    mergeRequestIid: 10,
  },
})
```

**TypeScript**

```ts
import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const result = await pd.actions.run({
  id: "gitlab-approve-merge-request",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    gitlab: { authProvisionId: "apn_xxxxxxx" },
    projectId: "Project",
    mergeRequestIid: 10,
  },
})

console.log(result)
```

**cURL**

```bash
curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
  -H "Content-Type: application/json" \
  -H "X-PD-Environment: production" \
  -H "Authorization: Bearer {access_token}" \
  -d '{
    "external_user_id": "{external_user_id}",
    "id": "gitlab-approve-merge-request",
    "configured_props": {
      "gitlab": { "authProvisionId": "apn_xxxxxxx" },
      "projectId": "Project",
      "mergeRequestIid": 10
    }
  }'
```

---

- App: https://pipedream.com/apps/gitlab.md · All apps: https://pipedream.com/apps