Test MCP Connection
Authentication
Enter your API key with the Bearer prefix, e.g. ‘Bearer sk_…’.
Request
Config shape for kind=mcp. The worker opens the
configured transport at session start, runs initialize +
list_tools, and registers each discovered remote tool as a
livekit-agents function_tool proxying through the long-lived
ClientSession.
Optional tool_<crockford> id of the existing tool to hydrate
stored secrets from. Raw UUIDs and other-resource prefixes are
rejected.
Response
Probe result. The 200 envelope is used for both success and
structured failure — inspect error to disambiguate. Network
and validation failures never bubble up as non-2xx so the
console can render them inline next to the form.
Structured upstream signal for an MCP probe failure. All fields
are optional; the console renders what’s present. stage names
the phase the probe was in (validation, oauth2_token,
mcp_connect, mcp_initialize, mcp_notify, mcp_list_tools).
oauth2_error / oauth2_error_description mirror RFC 6749 §5.2
when the customer’s auth server returned the standard error
shape. http_status is the upstream status code for transport
failures. upstream_body is a truncated prefix (max ~1 KiB) of
the upstream response body when the failure isn’t structured.
field_hint names a form field (endpoint, transport,
token, token_url, client_id, client_secret, scope)
the console should highlight so the customer knows what to fix.