Get a client
One client’s full settings, including its resolved config, its configId (the concurrency token every write takes), and impact — what a config edit would follow. The path segment accepts a client name or ID. A client that exists but belongs to a different project reads as 404 NOT_FOUND.
Authorizations
MCPJam API key (sk_…). Create one at Settings → API keys. Guest sessions cannot use the API, and API keys cannot manage other API keys.
Path Parameters
ID of the hosted project that contains the server.
Client name or ID. A name is matched case-insensitively and must be unique in the project; an ambiguous name is refused with 409 CONFLICT listing the candidate ids rather than resolved to one of them.
Query Parameters
Include clients that exist only as the private backing of a User Testing scenario. Excluded by default, matching the Clients tab; this is an administrative opt-in and applies to name resolution as well as to listing.
Response
The client settings.
A client plus its resolved config (model, capabilities, host context, MCP profile) and the read-backs an editor needs.
Client config v2 DTO. Opaque object; shape mirrors the inspector's client editor.
The concurrency token — see Client.configId.
Unix epoch milliseconds.
Unix epoch milliseconds.
What a config edit to this client would follow. These are the DURABLE consumers that re-resolve the client's current config; past runs, per-turn traces and pinned eval-suite snapshots hold a config id and are unaffected. Direct playground and client-chat use follows the edit too and has no row to count.

