# custom_emoji — gitlab

> 3 actions
> This page as plain markdown. Index: https://mcp.jmrp.io/llms.txt

Canonical: https://mcp.jmrp.io/servers/gitlab/actions/custom_emoji/
Language: en
Alternate: https://mcp.jmrp.io/es/servers/gitlab/actions/custom_emoji/index.md
Updated: 2026-09-11T09:56:41+02:00
License: https://mcp.jmrp.io/license/

Counted with a Free-tier token against gitlab.com, which is the only host this endpoint talks to: to use it against a self-managed instance, run the server yourself — its documentation covers that. The catalog is scoped to the token that asks, so the count moves with both its tier and its permissions: higher tiers expose more actions, and administration domains only appear to tokens allowed to use them. That is why the figures differ elsewhere: the upstream project catalogues 1,006 actions across 162 domains, and 851 on the Free/CE surface, while this deployment publishes 747 because it is OAuth-only and acts with your token, so the administration domains a non-admin account cannot call never appear. All three describe the same catalog, counted from three vantage points.

## Actions

### `custom_emoji.create` — Create Custom Emoji

Create group-level custom emoji using GraphQL-backed routes.

**Required parameters:** `group_path (string)`, `name (string)`, `url (string)`

### `custom_emoji.delete` — Delete Custom Emoji

_destructive_

Delete group-level custom emoji using GraphQL-backed routes.

**Required parameters:** `id (string)`

### `custom_emoji.list` — List Custom Emoji

_read-only_

List group-level custom emoji using GraphQL-backed routes.

**Required parameters:** `group_path (string)`