Create a client (from a template or a full config)
Creates a client in the project and responds 201 with the new client’s detail. Seed the config one of two ways: pass template (a built-in template id, optional theme) to seed server-side from the live backend client-template catalog, falling back to the bundled SDK catalog snapshot if the live catalog is unavailable, OR pass config (a full client config v2). Exactly one of template or config is required.
Guest callers are denied (client creation is a write).
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.
Body
- Option 1
- Option 2
Create a client from a built-in template OR a full config. Exactly one of template or config is required.
Display name for the new client.
Built-in template id to seed the host config from.
mcpjam, claude, claude-code, chatgpt, mistral, cursor, codex, copilot, vscode, agentcore, n8n, perplexity Theme stamped into the seeded config (template only).
light, dark Full client config v2, used verbatim (alternative to template). Must pin modelId.
Response
The client was created.
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.

