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

# List connectors

> List the workspace's connectors — the vetted catalog and its own custom MCP servers — with whether the key's member has each connected. **Requires scope:** `connectors:read`.



## OpenAPI

````yaml /openapi-v1.json get /v1/connectors
openapi: 3.1.0
info:
  title: Custral API
  version: v1
  description: >-
    The curated, versioned, API-key-authenticated public REST surface (`/v1`).
    Every endpoint here is what the official SDKs (`@custral/sdk`) and the MCP
    server are built on. Authenticate with a secret API key (`sk_…`) created in
    **Settings → Applications**.
  contact:
    name: Custral Support
    email: hello@custral.com
    url: https://custral.com
  license:
    name: Proprietary
    url: https://custral.com
servers:
  - url: https://api.custral.com
    description: Production
security:
  - ApiKey: []
tags:
  - name: Identity
    description: Introspect the calling API key.
  - name: Records
    description: Create, list, retrieve, and update records on any object.
  - name: Objects
    description: Read the object (table) schema of your workspace.
  - name: Conversations
    description: View, manage, and ingest conversations and their messages.
  - name: MCP
    description: Introspect the Model Context Protocol tool surface for a key.
  - name: Documents
    description: Read record notes / page documents as markdown.
  - name: Connectors
    description: The MCP servers Stella can use tools from.
paths:
  /v1/connectors:
    get:
      tags:
        - Connectors
      summary: List connectors
      description: >-
        List the workspace's connectors — the vetted catalog and its own custom
        MCP servers — with whether the key's member has each connected.
        **Requires scope:** `connectors:read`.
      operationId: listConnectors
      responses:
        '200':
          description: The connectors.
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/Connector'
                  reqId:
                    $ref: '#/components/schemas/RequestId'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
components:
  schemas:
    Connector:
      type: object
      description: >-
        A connector: an MCP server Stella can use tools from — a vetted catalog
        entry or the workspace's own custom server.
      properties:
        id:
          type: string
          description: >-
            The connector id — a catalog id (`slack`) or a custom connector's
            (`c-linear-3f2a`).
          example: slack
        name:
          type: string
          example: Slack
        description:
          type: string
        custom:
          type: boolean
          description: A workspace's own MCP server rather than a vetted catalog entry.
        host:
          type:
            - string
            - 'null'
          description: The server's hostname (custom connectors only).
        authType:
          type: string
          enum:
            - oauth
            - token
            - none
        connectionScope:
          type: string
          enum:
            - org
            - user
          description: >-
            `org` = one shared connection; `user` = each member connects their
            own.
        connected:
          type: boolean
          description: Whether the key's member has it connected.
        status:
          type:
            - string
            - 'null'
          enum:
            - active
            - errored
            - null
        enabled:
          type: boolean
        allowWrites:
          type: boolean
          description: >-
            Whether Stella may use its write tools (each call still asks for
            approval).
    RequestId:
      type: string
      description: >-
        A per-request id (`req_…`). Quote it to support when reporting a
        problem.
      example: req_2a1f9c8e7b6d5
    Error:
      type: object
      description: >-
        The failure envelope. Every error carries a machine-readable `code` and
        the `reqId` of the failing request.
      properties:
        error:
          type: object
          properties:
            code:
              type: string
              example: insufficient_scope
          required:
            - code
        reqId:
          $ref: '#/components/schemas/RequestId'
      required:
        - error
  responses:
    Unauthorized:
      description: >-
        The API key is missing, unknown, inactive, or expired (`code:
        invalid_api_key`).
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              code: invalid_api_key
            reqId: req_2a1f9c8e7b6d5
    Forbidden:
      description: >-
        The key lacks the scope this endpoint requires (`code:
        insufficient_scope`).
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              code: insufficient_scope
            reqId: req_2a1f9c8e7b6d5
  securitySchemes:
    ApiKey:
      type: http
      scheme: bearer
      bearerFormat: sk_...
      description: >-
        A Custral **secret** API key (`sk_…`), created in Settings →
        Applications. Sent as `Authorization: Bearer sk_…`. The `X-Api-Key:
        sk_…` header is also accepted and takes precedence. Never expose a
        secret key in a browser.

````

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