> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getprimo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 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.

Key: ReadScope: Company


## OpenAPI

````yaml https://api.getprimo.com/openapi.json get /mcp-gateway/connectors/{connectorId}
openapi: 3.1.1
info:
  title: Public API - BETA
  description: Read docs on https://docs.getprimo.com/
  version: '1.0'
  contact: {}
servers:
  - url: https://api.getprimo.com
security:
  - apikey: []
tags: []
paths:
  /mcp-gateway/connectors/{connectorId}:
    get:
      tags:
        - McpGateway
      summary: Get one MCP Gateway connector
      description: >-
        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.
      operationId: getMcpGatewayConnector
      parameters:
        - name: connectorId
          required: true
          in: path
          schema:
            type: string
      responses:
        default:
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetMcpGatewayConnectorResponse_Output'
components:
  schemas:
    GetMcpGatewayConnectorResponse_Output:
      type: object
      properties:
        id:
          type: string
        name:
          type: string
        toolPrefix:
          description: What the names of its tools start with
          type: string
        source:
          description: '`catalog` (an entry of the catalog) or `custom` (an address)'
          type: string
          enum:
            - catalog
            - custom
        catalogKey:
          description: The `key` of its catalog entry, null for a custom connector
          anyOf:
            - type: string
            - type: 'null'
        serverUrl:
          description: The origin and the path of the server, never its query or fragment
          type: string
        transport:
          description: >-
            How the gateway talks to the server: `streamable_http`, or `sse` for
            an older server
          type: string
          enum:
            - streamable_http
            - sse
        authentication:
          description: >-
            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
          anyOf:
            - type: object
              properties:
                type:
                  type: string
                  const: oauth_dynamic
                scopes:
                  type: array
                  items:
                    type: string
              required:
                - type
                - scopes
              additionalProperties: false
            - type: object
              properties:
                type:
                  type: string
                  const: oauth_client
                clientId:
                  type: string
                scopes:
                  type: array
                  items:
                    type: string
              required:
                - type
                - clientId
                - scopes
              additionalProperties: false
            - type: object
              properties:
                type:
                  type: string
                  const: header_token
                headerName:
                  type: string
                scheme:
                  anyOf:
                    - type: string
                    - type: 'null'
              required:
                - type
                - headerName
                - scheme
              additionalProperties: false
            - type: object
              properties:
                type:
                  type: string
                  const: custom_headers
                headerNames:
                  type: array
                  items:
                    type: string
              required:
                - type
                - headerNames
              additionalProperties: false
            - type: object
              properties:
                type:
                  type: string
                  const: none
              required:
                - type
              additionalProperties: false
        credentialMode:
          description: >-
            `per_employee`: each employee connects their own account; `shared`:
            IT connects one account that every employee uses
          type: string
          enum:
            - per_employee
            - shared
        enabled:
          description: Whether employees are served its tools; IT enables it in the cockpit
          type: boolean
        createdAt:
          type: string
        updatedAt:
          type: string
        listedToolCount:
          description: How many tools its snapshot lists
          type: integer
          minimum: -9007199254740991
          maximum: 9007199254740991
        setupStatus:
          description: >-
            The first thing IT still has to do in the cockpit before it serves
            its tools, or `ready`
          type: string
          enum:
            - disabled
            - no_tools_listed
            - shared_credential_missing
            - shared_credential_to_reconnect
            - employees_connect_themselves
            - ready
        cockpitUrl:
          description: Its page in the cockpit, where IT finishes its setup
          type: string
      required:
        - id
        - name
        - toolPrefix
        - source
        - catalogKey
        - serverUrl
        - transport
        - authentication
        - credentialMode
        - enabled
        - createdAt
        - updatedAt
        - listedToolCount
        - setupStatus
        - cockpitUrl
      additionalProperties: false
  securitySchemes:
    apikey:
      scheme: bearer
      bearerFormat: API key
      type: http
      description: >-
        Use your Primo API key in the Authorization header as `Bearer
        <API_KEY>`.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.