---
title: "corestack_company_deployment_connections_list"
url: https://docs.corefinity.com/mcp/tools/corestack_company_deployment_connections_list
type: tool
last_updated: 2026-11-13
feature: deployment-connections
related:
  - https://docs.corefinity.com/guides/organisation/developers/repository-connections.md
---
# corestack_company_deployment_connections_list

**Your company's deployment connections.** List your company's deployment connections (the GitHub, GitLab and Bitbucket accounts its environments deploy from), oldest first, 50 a page: each one's account, status, since when it needs re-authorising, the link that reconnects it and the environments that deploy through it. Scope: read.

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

## When to use it

List your company's deployment connections: the GitHub, GitLab, Bitbucket and self-hosted GitLab accounts its environments deploy from, oldest first, 50 a page. Use it when a deployment fails at checking out the repository, when a webhook says the account must be reconnected, or before removing a connection.

Each connection shows its provider, the account it signs in as (`username`), when it was connected and its `status`: `connected`, or `needs_reauthorisation` with `needs_reauth_since`. A connection that needs re-authorising cannot clone or install webhooks until it is reconnected. To reconnect a GitHub, GitLab or Bitbucket connection, give the person `reconnect_url` to open in a browser where they are signed in to the Control Panel; they must sign in to the provider as `username`, because another account adds a new connection instead of repairing this one. Self-hosted GitLab has no link (`reconnect_url` is null): the person creates a new personal access token and uses Replace access token on the connection in the Control Panel. `reconnect_note` says this in plain words.

A GitHub connection also has `organisation_access_url`: GitHub's page where an organisation grants the Control Panel access to its repositories, or a member asks for it. GitHub asks about organisations only the first time someone connects, so when an organisation's repositories are missing from `corestack_deployments_repositories_list`, give the person this link to open in a browser signed in to GitHub as `username`. It is null for GitLab, Bitbucket and self-hosted GitLab.

`environments` names the live environments that deploy through the connection; `other_environments` counts the ones not named to you (hidden ones, and for a token limited to some sites, those outside its limits). `can_remove` is true when you may remove the connection and nothing deploys through it.

## Inputs

- `cursor` (string, optional): the `next_cursor` of the page before; null there means the last page.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "cursor": {
      "description": "The next_cursor of the page before.",
      "maxLength": 20,
      "type": "string"
    }
  },
  "type": "object"
}
```

## Refusals

- `invalid_arguments`: a cursor that is not one of ours; start again from the first page.
- The refusals every tool can answer: `invalid_arguments`, `tenant_mismatch`, `scope_required`, `pin_refused`, `rate_limited`, `temporarily_unavailable`, `internal_error` (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_company_deployment_connections_list",
  "arguments": {}
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_company_deployment_connections_list. (Your company's deployment connections.) Tell me what it returned.
```

## The same task elsewhere

- Guide: [Repository connections](https://docs.corefinity.com/guides/organisation/developers/repository-connections.md)
