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

# miniDesk.ai

> One shared inbox for every customer question, from chat, forms and email. AI drafts the replies.

miniDesk is a support desk. A chat widget on your site, a contact form, an
email address: pick any of them, and your customers' questions all arrive in one
inbox. Your team works from there.

Replies can be drafted by AI, using your own reference documents as the source.
You decide if it just suggests an answer or sends one out.

## What you can build against

Two entry points, aimed at different callers.

<CardGroup cols={2}>
  <Card title="REST API" icon="code" href="/api-reference/introduction">
    For your own systems. Raise a ticket when a job fails, sync a reply into
    your CRM, or move a conversation along when a customer upgrades.
  </Card>

  <Card title="MCP server" icon="robot" href="/mcp/overview">
    For AI agents. Let Claude or ChatGPT look through your queue, search your
    reference documents, and prepare a draft reply for review.
  </Card>
</CardGroup>

Auth is per workspace on both, and one workspace can never read another's data.
They also share a single error envelope.

## The pieces

<Steps>
  <Step title="A workspace">
    One holds everything. Your team, tickets, reference documents, and API keys
    all live here.
  </Step>

  <Step title="Channels">
    How conversations arrive. A chat widget, a contact form, an email address,
    or the API. Run all of them at once if you like; they all land in one inbox.
  </Step>

  <Step title="Tickets">
    A single conversation with a single person. No subject line is needed. The
    first message defines the ticket, and the requester is the identity.
  </Step>

  <Step title="Messages">
    `public` ones reach the customer on their original channel. `internal`
    ones are notes for your team only. Neither the API nor the MCP server will
    ever return an internal note.
  </Step>
</Steps>

## A note on what the AI can and cannot do

Read this before connecting anything, because the whole API surface follows
from it.

An AI agent on MCP can **read** your queue and **write a draft**. Sending is
off the table. You cannot grant that as a permission: no send tool exists, and
the only path from draft to real message goes through a person pressing send or
through an automation gate.

That means a connected agent cannot be manipulated into emailing your
customers, not even by a hostile ticket body. [The reasoning is written up
here](/mcp/safety).

## Start here

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Grab a key, open your first ticket. Five minutes, give or take.
  </Card>

  <Card title="Set up a channel" icon="inbox" href="/channels/overview">
    Put chat on your site, add a contact form, or forward a support address.
  </Card>
</CardGroup>