Does team mean the same thing on each platform?

Roughly, but the scope differs. On Linear a team groups issues and projects; on Mattermost it groups channels; on Heroku it scopes apps and access; on Grafana it groups dashboards and permissions. The list call is the same idea on each: return the teams so an agent can target one by id.

Why list teams before acting?

To get the id. Assigning work, posting to a team space, or reporting on a group references the team by id, not its display name. Listing resolves the name to the id, so an agent's action lands on the right team.

MCP servers that can list teams

4 verified servers expose a tool that can list teams in a workspace

Teams are how most platforms group people, and an agent that assigns work, reports on a group, or scopes an action by team first has to list them. Listing teams returns the groups in a workspace or org, so the agent can resolve a team name to the id its other tools want.

These verified servers let an agent list the teams in a workspace.

Top pick

Linear

Official

Linear's official remote MCP server lets agents create, search, and update issues and projects.

productivity

Tool:

list_teams

Linear groups issues and projects by team, so list_teams returns those teams, the lookup before an agent assigns or files work in the right one.

Pick 2

Mattermost

cloud.ru (community)

Community

A maintained MCP server for Mattermost that lets agents work with channels, messages, threads, reactions, users, teams, and files.

communication30

Tool:

list_teams

On Mattermost, channels live under teams, and list_teams returns them so an agent can target the right team's space.

Pick 3

Heroku

Heroku (Salesforce)

Official

Heroku's official Platform MCP server: deploy apps, scale dynos, manage add-ons and pipelines, run one-off commands, and operate Postgres from your agent.

cloud-infra

Tool:

list_teams

Heroku scopes apps and access to a team: list_teams returns the teams the account belongs to, the grouping behind its permissions.

Pick 4

Grafana

Grafana Labs

Official

Grafana Labs' official MCP server: query dashboards, Prometheus, Loki, incidents, alerts, and OnCall from your agent.

monitoring-observability3,083

Tool:

list_teams

Grafana's list_teams returns its configured teams, an admin call that is off by default, the groups its dashboards and permissions hang off.

What to know

A team list is the lookup behind anything team-scoped: assign an issue to a team, post to a team's channel, report who is on one. The platforms here mean slightly different things by team, but the call is the same: return the groups the connection can see. Linear groups issues and projects by team; Mattermost organizes channels under teams; Heroku scopes apps and access to a team; Grafana groups dashboards and permissions. The list resolves a human team name to the id the action tools reference.

Team structure changes slowly, so an agent that learns the teams and their ids once can hold that rather than re-list each session. Knowing which team owns what lets it route an assignment or a report to the right group without re-enumerating every time.

Questions

Does team mean the same thing on each platform?: Roughly, but the scope differs. On Linear a team groups issues and projects; on Mattermost it groups channels; on Heroku it scopes apps and access; on Grafana it groups dashboards and permissions. The list call is the same idea on each: return the teams so an agent can target one by id.
Why list teams before acting?: To get the id. Assigning work, posting to a team space, or reporting on a group references the team by id, not its display name. Listing resolves the name to the id, so an agent's action lands on the right team.