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

# Claude

> Connect miniDesk to Claude Desktop, claude.ai, or Claude Code.

## Get a token first

In the dashboard, go to **Settings → MCP** and create a credential. It starts
with `mdsk_mcp_` and is shown once, so keep it somewhere before you close the
dialog.

## Claude Desktop

<Steps>
  <Step title="Open the config file">
    **Settings → Developer → Edit Config**, which opens
    `claude_desktop_config.json`.
  </Step>

  <Step title="Add the server">
    ```json theme={null}
    {
      "mcpServers": {
        "minidesk": {
          "url": "https://api.minidesk.ai/mcp",
          "headers": {
            "Authorization": "Bearer mdsk_mcp_YOUR_TOKEN"
          }
        }
      }
    }
    ```

    If you already have other servers, add `minidesk` alongside them rather
    than replacing the object.
  </Step>

  <Step title="Restart Claude">
    Fully quit and reopen. The tools appear in the tools menu once it comes
    back.
  </Step>
</Steps>

## claude.ai

<Steps>
  <Step title="Open connector settings">
    **Settings → Connectors → Add custom connector**.
  </Step>

  <Step title="Enter the server URL">
    `https://api.minidesk.ai/mcp`
  </Step>

  <Step title="Add the authorization header">
    Name `Authorization`, value `Bearer mdsk_mcp_YOUR_TOKEN`.
  </Step>
</Steps>

## Claude Code

```bash theme={null}
claude mcp add --transport http minidesk https://api.minidesk.ai/mcp \
  --header "Authorization: Bearer mdsk_mcp_YOUR_TOKEN"
```

Check it connected with `/mcp` inside a session.

## Try it

Once connected, ask in plain language:

> What is waiting in support right now?

> Read ticket ACME-1042, check our refund policy, and draft a reply.

> Who has the most open conversations?

Claude picks the right tool from the descriptions, so you do not need to name
them.

## Confirm what it can do

Ask it to send something and it will tell you it cannot. That is expected:
there is no send tool, so the queue is safe to connect to a production
workspace. See [what an agent cannot do](/mcp/safety).

## If it does not appear

<AccordionGroup>
  <Accordion title="No tools show up">
    Almost always the header. It must be `Authorization` with the value
    `Bearer mdsk_mcp_...`, including the word `Bearer` and one space.
  </Accordion>

  <Accordion title="Everything returns an auth error">
    Check the token is an **MCP** credential and not an API one. An
    `mdsk_api_` token is rejected by this endpoint by design. Also check it has
    not been revoked in **Settings → MCP**.
  </Accordion>

  <Accordion title="Claude Desktop ignores the config">
    Validate the JSON. A trailing comma silently stops the whole file loading,
    and Claude shows no error for it.
  </Accordion>
</AccordionGroup>