Add an MCP Gateway connector
Add a connector and return it with its setupStatus and cockpitUrl. definition.source catalog takes a catalogKey from getMcpGatewayCatalog, a credentialMode the entry supports, and optionally a name and a toolPrefix (the entry’s by default). custom takes a name, a toolPrefix, the serverUrl (https, origin and path: a query or a fragment is refused with a 400, so a token never travels in the address), the transport, the authentication (its type and header names or OAuth client id, never a secret) and the credentialMode. A catalog connector starts enabled; a custom one starts disabled, until IT reads its tools and enables it in the cockpit. Either way no tool is served before IT lists its tools there, and connects the account of a shared one. A 404 means the catalog key is unknown, a 409 that the tool prefix is taken. Nothing here changes or enables an existing connector: that is done in the cockpit. 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