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

# ChatGPT

> Connect miniDesk to ChatGPT as a custom connector.

## Get a token first

In the dashboard, go to **Settings → MCP** and create a credential. It starts
with `mdsk_mcp_` and is shown once.

## Add the connector

<Steps>
  <Step title="Open connector settings">
    **Settings → Connectors → Create**. You need a plan that includes custom
    connectors, and on a workspace account an admin may need to allow them
    first.
  </Step>

  <Step title="Fill in the server">
    | Field          | Value                         |
    | -------------- | ----------------------------- |
    | Name           | `miniDesk`                    |
    | MCP server URL | `https://api.minidesk.ai/mcp` |
    | Authentication | Custom header                 |
    | Header name    | `Authorization`               |
    | Header value   | `Bearer mdsk_mcp_YOUR_TOKEN`  |
  </Step>

  <Step title="Save and enable it">
    Turn the connector on in the composer for the conversations where you want
    it.
  </Step>
</Steps>

## Try it

> Summarise what is waiting in support.

> Which conversations have been waiting longest, and what are they about?

> Read ticket ACME-1042 and draft a reply using our documentation.

## What it can and cannot do

It can read your queue, read conversations, search your reference documents,
and write a draft for review.

It cannot send a reply, change a status, or assign anything. Those tools do
not exist, which is why connecting a production workspace is safe. See
[what an agent cannot do](/mcp/safety).

## If it does not work

<AccordionGroup>
  <Accordion title="The connector will not save">
    ChatGPT validates the server on save. Check the URL has no trailing slash
    and that the header value begins with `Bearer ` including the space.
  </Accordion>

  <Accordion title="Tools are listed but every call fails">
    The token is probably an API credential rather than an MCP one. They are
    not interchangeable: `mdsk_api_` is rejected here on purpose.
  </Accordion>

  <Accordion title="Custom connectors are not available">
    They are gated by plan and, on workspace accounts, by an admin setting.
    That is on OpenAI's side, not ours.
  </Accordion>
</AccordionGroup>