---
title: "corestack_ticket_subscribers_list"
url: https://docs.corefinity.com/mcp/tools/corestack_ticket_subscribers_list
type: tool
last_updated: 2026-11-13
feature: support
related:
  - https://docs.corefinity.com/guides/support/raise-and-follow-a-ticket.md
---
# corestack_ticket_subscribers_list

**List who follows a support ticket.** List who follows a support ticket and is told of its replies, as the ticket page's Subscribers box. With search, also who you may add. Scope: read.

- Scope: `read`
- Runs as a task: no

## When to use it

See who follows a support ticket, as the ticket page's Subscribers box shows them. Followers are told of the ticket's
replies. `can_manage` says whether you may change them (corestack_ticket_subscriber_add and
corestack_ticket_subscriber_remove). Add `search` to also list the people you may add, as the page's picker offers them.

## Inputs

- `ticket_id` (integer, ≥ 1, required): the ticket's number, from corestack_tickets_list.
- `search` (string, ≤ 255, optional): part of a person's name. It lists up to six active people from the companies that
  may follow the ticket: for an agency, the ticket's client company and the agency itself; for a client, its own company.
  An empty string lists the first six.
- `client_company_id` (integer, optional): the client company the ticket is in, when your agency raised it for a client
  (the same value you listed it with); your own company when left out.

The answer is `{ticket_id, can_manage, subscribers[], candidates[]?}`. Each person is `{id, name, email, company_name}`,
and `candidates` is there only when you sent `search`.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "client_company_id": {
      "minimum": 1,
      "type": "integer"
    },
    "search": {
      "maxLength": 255,
      "type": "string"
    },
    "ticket_id": {
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "ticket_id"
  ],
  "type": "object"
}
```

## Refusals

- `tenant_mismatch`: there is no such ticket, or it is not in your company (or in `client_company_id`, a client company
  your agency reaches), or the person only follows it as a subscriber of another company.
- `forbidden`: you sent `search`, but you may not change who follows this ticket.
- `pin_refused`: the token is limited to some sites; a ticket belongs to the whole company.
- The refusals every tool can answer: `invalid_arguments`, `scope_required`, `rate_limited`, `temporarily_unavailable`,
  `internal_error` (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_ticket_subscribers_list",
  "arguments": {
    "ticket_id": 48210,
    "search": "Sam"
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_ticket_subscribers_list with ticket_id 48210, search Sam. (List who follows a support ticket.) Tell me what it returned.
```

## The same task elsewhere

- Guide: [Support tickets](https://docs.corefinity.com/guides/support/raise-and-follow-a-ticket.md)
