---
title: "corestack_deployments_repositories_list"
url: https://docs.corefinity.com/mcp/tools/corestack_deployments_repositories_list
type: tool
last_updated: 2026-11-13
feature: deployments
related:
  - https://docs.corefinity.com/api/reference/deployments/list-site-deployment-repositories.md
  - https://docs.corefinity.com/guides/sites/code-and-deployments/connect-a-repository.md
---
# corestack_deployments_repositories_list

**Repositories.** The repositories one of the company's Git connections can deploy from, optionally searched. Scope: read.

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

## When to use it

The repositories one of the Git connections you may use on the site can deploy from, optionally searched: at most 50, most recently updated first.

On GitHub this includes the repositories of the organisations the account belongs to, once the organisation has granted the Control Panel access. When an organisation's repositories are missing, the connection's `organisation_access_url` (`corestack_company_deployment_connections_list`) is GitHub's page where the organisation grants that access, or a member asks for it.

On Bitbucket this includes the repositories of every workspace the account belongs to. When one workspace does not answer, it is left out and the others are listed.

## Inputs

- `site_id` (integer, ≥ 1, required)
- `connection` (integer, ≥ 1, required): A Git connection's id (corestack_deployments_get lists them).
- `q` (string, up to 100 characters): Part of a repository's name.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "connection": {
      "description": "A Git connection's id (corestack_deployments_get lists them).",
      "minimum": 1,
      "type": "integer"
    },
    "q": {
      "description": "Part of a repository's name.",
      "maxLength": 100,
      "type": "string"
    },
    "site_id": {
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "site_id",
    "connection"
  ],
  "type": "object"
}
```

## Refusals

- `needs_reauth`: the provider refused the connection's sign-in and a refresh could not renew it ("The Bitbucket connection needs re-authorising"). Connect the account again in the Control Panel, then list again.
- `upstream_unavailable`: the provider did not answer ("Bitbucket did not answer. Try again."), or on Bitbucket none of the account's workspaces answered. Try again in a moment.
- `tenant_mismatch`: the connection is not one you may use on this site — another company's, or one belonging to an agency that manages the site (its accounts are the agency's people's). `corestack_deployments_get` lists the connections you may use.
- 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_deployments_repositories_list",
  "arguments": {
    "site_id": 4211,
    "connection": 12
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_deployments_repositories_list with site_id 4211, connection 12. (Repositories.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [GET /api/corestack/sites/{site}/deployments/repositories](https://docs.corefinity.com/api/reference/deployments/list-site-deployment-repositories.md)
- Guide: [Connect a repository](https://docs.corefinity.com/guides/sites/code-and-deployments/connect-a-repository.md)
