---
title: "List a project's clients"
method: GET
path: "/projects/{projectId}/clients"
tags: ["Clients"]
---

# List a project's clients

`GET /projects/{projectId}/clients`

The clients saved in the project — the named, reusable configurations that define how MCPJam connects to and talks to your MCP servers. Returns the `id`s and `configId`s the detail and write routes take. Clients that exist only as the private backing of a User Testing scenario are omitted unless `includePrivateBacking=true`.

## Path parameters

- `projectId` string, required

## Query parameters

- `includePrivateBacking` boolean

## Response `200`

The project's clients.

- ClientPage
  - `items` Client[], required
    - `id` string, required
    - `name` string, required
    - `configId` string, required — ID of the content-addressed config this client points at. Content addressed, so the same id means byte-identical settings — send it back as `expectedConfigId` on a write to make the write compare-and-set.
    - `modelId` string, required — Resolved model id, e.g. `anthropic/claude-haiku-4.5`.
    - `serverCount` integer, required — Number of MCP servers attached to the client config.
    - `ownerScope` object, nullable, required — Product ownership of the row (null for untagged clients). Never an authorization signal.
    - `hasComputer` boolean, required — Whether the live config attaches a computer.
    - `createdAt` number, required — Unix epoch milliseconds.
    - `updatedAt` number, required — Unix epoch milliseconds.

## Other responses

- `401` — Missing, invalid, revoked, or orphaned key (`UNAUTHORIZED`) — or the **target MCP server** needs an OAuth grant (`OAUTH_REQUIRED`), which is a property of the server, not your key.
- `403` — Key is valid but not allowed to do this.
- `404` — Unknown project, server, or resource.
- `409` — The resource is not in a state that accepts this write — a stale `expectedRevision`, a duplicate name, or an environment that cannot currently be launched. The request was well-formed; re-read the resource and retry.
- `429` — Per-key rate limit exceeded (60 requests/minute sustained, bursts up to 10). Honor `Retry-After` and back off with jitter.
- `500` — Something failed on MCPJam's side.
- `502` — Could not connect to the target MCP server.

---

[API](https://skmtc.dev/mcpjam/apis/mcpjam-api.md) · [All operations](https://skmtc.dev/mcpjam/apis/mcpjam-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/mcpjam/mcpjam-api/revisions/c628a0e95b06/schema)