# add_project_member (/docs/reference/mcp-tools/add_project_member)



{/* Generated by apps/docs/scripts/generate-mcp-pages.mjs — do not edit by hand. */}

Add a member to a project at a role (ADMIN/MEMBER/VIEWER).

|                     |                        |
| ------------------- | ---------------------- |
| Required permission | `work:write`           |
| Capability ID       | `projects.members.add` |
| Destructive         | No                     |

## Parameters [#parameters]

| Parameter   | Type                            | Required | Notes |
| ----------- | ------------------------------- | -------- | ----- |
| `userId`    | string (uuid)                   | yes      |       |
| `role`      | `ADMIN` \| `MEMBER` \| `VIEWER` | no       |       |
| `projectId` | string (uuid)                   | yes      |       |

## Input schema (JSON Schema) [#input-schema-json-schema]

```json
{
  "type": "object",
  "properties": {
    "userId": {
      "type": "string",
      "format": "uuid"
    },
    "role": {
      "type": "string",
      "enum": [
        "ADMIN",
        "MEMBER",
        "VIEWER"
      ],
      "default": "MEMBER"
    },
    "projectId": {
      "type": "string",
      "format": "uuid"
    }
  },
  "required": [
    "userId",
    "projectId"
  ],
  "additionalProperties": false
}
```

## Access control [#access-control]

A call succeeds only when the personal access token's scopes **and** the holder's role both allow `work:write` (effective permission = scope ∩ role, default-deny). The tool runs inside the token owner's organization — tenancy is never a parameter.