Why list labels before applying one?

To apply an existing category rather than invent a new one. Listing shows the labels a project already defines, so an agent tags with a real one instead of minting a near-duplicate. It is also how an agent filters: pull every item carrying a given label by its id.

What scope are the labels at?

It varies by tracker. GitHub's are per-repository, Plane's per-project, Gitea's per-organization, Shortcut's per-workspace. An agent lists at the scope it is working in to get the labels that actually apply to the items there.

MCP servers that can list labels

4 verified servers expose a tool that can list labels

Before an agent tags something or filters by category, it has to know which labels exist. Listing labels returns the available tags, so the agent applies a real one, urgent, bug, frontend, rather than inventing a near-duplicate that splits the bucket.

These verified servers let an agent list the labels in a project or repository.

Top pick

GitHub

Official

GitHub's official remote MCP server for repos, issues, pull requests, Actions, and code search.

version-control30,334

Tool:

list_label

GitHub's list_label returns the labels defined in a repository, the categories an agent picks from before tagging an issue or PR.

Pick 2

Plane

Official

Plane's official MCP server exposes its full project API — work items, cycles, modules, and more — to agents.

project-management235

Tool:

list_labels

On Plane, list_labels returns a project's labels, the tags an agent applies to or filters work items by.

Pick 3

Gitea

Official

Gitea's official MCP server for repos, branches, issues, pull request reviews, releases, Actions, and wikis on any Gitea instance.

version-control73

Tool:

list_org_labels

Across the repos in an organization, list_org_labels returns Gitea's shared labels on a self-hosted instance.

Pick 4

Shortcut

Official

Shortcut's official MCP server: find, create, and update Stories, Epics, Iterations, Objectives, and Docs from your agent.

project-management98

Tool:

labels-list

For categorizing a story, labels-list returns the workspace's labels in Shortcut.

What to know

A label list is the lookup behind tagging and filtering. To apply the right category to an issue, or to pull every card with a given tag, an agent first reads the labels the project defines. The trackers here return them at their natural scope: GitHub the labels in a repository, Plane the labels in a project, Gitea an organization's labels, Shortcut the workspace's. From the list the agent picks an existing label by id or name, which keeps it from creating urgent when Urgent already exists.

The label set is stable, so an agent that learns it once can hold it rather than re-list each time it tags something. Remembering the available categories is also what lets it apply them consistently, the difference between a board you can filter cleanly and one cluttered with near-duplicate tags.

Questions

Why list labels before applying one?: To apply an existing category rather than invent a new one. Listing shows the labels a project already defines, so an agent tags with a real one instead of minting a near-duplicate. It is also how an agent filters: pull every item carrying a given label by its id.
What scope are the labels at?: It varies by tracker. GitHub's are per-repository, Plane's per-project, Gitea's per-organization, Shortcut's per-workspace. An agent lists at the scope it is working in to get the labels that actually apply to the items there.