List MCP servers
Authentication
Query parameters
Maximum number of servers to return (1–100). Invalid values are rejected with 400, not clamped.
Number of servers to skip (0–100000). Invalid values are rejected with 400.
Maximum number of servers to return (1–100). Invalid values are rejected with 400, not clamped.
Number of servers to skip (0–100000). Invalid values are rejected with 400.
Returns the MCP servers the workspace manages, newest first by created_at. Excluded: the
platform’s per-agent gateway rows (see GET /api/agents/{agentId}/mcp-servers) and the
connected-apps tool surface managed under Integrations. Credentials, custom headers and
per-tool decisions are never included; GET /api/mcp-servers/{mcpServerId} adds
toolOverrides.
Offset pagination with limit and offset. The response has no pagination metadata:
request the next page until one comes back with fewer than limit items. See
Pagination.
Consistency. Pages are cached for up to 5 minutes; creating, updating, deleting or (un)assigning a server clears them before responding.
Idempotency. Read-only and safe to retry.
Access
read (or write). Any workspace role.Workspace API key: jl_ followed by 64 lowercase hex characters, created by the workspace owner in the
dashboard (Settings → API Keys) and sent as Authorization: Bearer jl_.... The plaintext is shown once,
at creation; Jelliu stores only a SHA-256 hash. A workspace can hold up to 25 active keys.
Operations restricted to admins or owners reject keys without the full scope with 403, and say so in
their description. No key, whatever its scope, can mint or revoke API keys or rotate a webhook secret —
that requires a signed-in owner session. A revoked key stops authenticating within about 10 seconds.
See Authentication.