Get one MCP Gateway connector
Return one MCP Gateway connector (connectorId from getMcpGatewayConnectors) with the same fields as the list, setupStatus and cockpitUrl included. setupStatus is the first thing IT still has to do in the cockpit before the connector serves its tools: disabled (enable it), no_tools_listed (list its tools), shared_credential_missing or shared_credential_to_reconnect (connect the shared account), employees_connect_themselves (each employee connects their own account) or ready. A 404 means the company has no such connector. The MCP Gateway serves employees, through their one Primo connection, the tools of the MCP servers (connectors) IT added. No credential is ever sent or returned here: IT connects a shared account, lists the tools and sets their policy in the cockpit, at cockpitUrl. A company without the MCP Gateway gets a 403 McpGatewayNotEnabledError; a 503 means Primo could not check it, try again in a minute.
Authorizations
Response
How the server is signed in to: OAuth (oauth_dynamic, or oauth_client with its client id), a token in a header (header_token, its header name and scheme), several headers (custom_headers, their names) or none. Never a secret: the credential itself is connected in the cockpit
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5