---
title: "corestack_enterprise_repositories_list"
url: https://docs.corefinity.com/mcp/tools/corestack_enterprise_repositories_list
type: tool
last_updated: 2026-11-13
feature: enterprise-deployments
related:
  - https://docs.corefinity.com/guides/corestack-enterprise/deployments-and-pipelines.md
---
# corestack_enterprise_repositories_list

**CoreStack Enterprise repositories.** A CoreStack Enterprise environment's git repositories and branches, and the git accounts a repository can be set up with. Scope: read.

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

## When to use it

List the git repositories and branches a CoreStack Enterprise environment deploys from, as its environment page's
Repositories field shows them to the person, and the git accounts they may set a repository up with (`connections`:
use one's `id` as `connection_id` in `corestack_enterprise_repository_set`).

A repository set up with a git account the person cannot use (another agency's, or their agency's when they are its
client) is listed with `connection_hidden: true` and no provider, repository, branch or root directory;
`connection_owner` names the agency that set it up only to its client.

`can_manage` and `can_set` say what your role may do with the repositories, each `{available, reason}`: `can_manage`
for `corestack_enterprise_repository_remove` (Manage Deployment Repositories), `can_set` for
`corestack_enterprise_repository_set` (that, and Create Deployments while a push deploys on its own). When one is not
available, `reason` is the sentence those tools refuse with, naming the permission and who can grant it.

The public API's `GET /api/environments/{environment}/repositories` and `.../repositories/connections` answer the same.
The repositories answer carries `can_manage` and `can_set` beside `environment_repositories`; the connections answer is
`connections` alone.

## Inputs

- `enterprise_env_id` (integer, ≥ 1, required)

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "enterprise_env_id": {
      "description": "A CoreStack Enterprise environment's id; for CoreStack or CoreCluster use the corestack_deployment_* tools.",
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "enterprise_env_id"
  ],
  "type": "object"
}
```

## Refusals

- `invalid_arguments` (field `enterprise_env_id`): a CoreStack or CoreCluster environment; use the
  `corestack_deployments_*` tools by `site_id`.
- `tenant_mismatch`, `pin_refused`, and the refusals every tool can answer: `scope_required`, `rate_limited`,
  `temporarily_unavailable`, `internal_error` (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_enterprise_repositories_list",
  "arguments": {
    "enterprise_env_id": 1530
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_enterprise_repositories_list with enterprise_env_id 1530. (CoreStack Enterprise repositories.) Tell me what it returned.
```

## The same task elsewhere

- Guide: [Deployments and pipelines](https://docs.corefinity.com/guides/corestack-enterprise/deployments-and-pipelines.md)
