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

# Introduction

> Connect an AI assistant to your NeetoDesk workspace over the Model Context Protocol.

NeetoDesk runs a hosted MCP server. Connecting an assistant to it lets you work on tickets by
asking in plain language, rather than switching to the web app or writing API calls.

Model Context Protocol is an open standard for exposing an application's data and actions to an
AI assistant. You do not need to know how it works to use it, and there is nothing to run or
host yourself.

## What an assistant can do

| Resource            | Abilities                                                                           |
| ------------------- | ----------------------------------------------------------------------------------- |
| Tickets             | List, search, read, create and update tickets                                       |
| Comments and drafts | List and read comments, post a reply or internal note, save a draft                 |
| Customers           | Create a customer                                                                   |
| Team members        | List, read, invite, update and deactivate members                                   |
| Forms               | List the workspace's enabled web forms                                              |
| Reports             | Ticket volume, daily time series, agent and group performance, satisfaction surveys |

The full list, with what each tool does, is on the [Tools](/mcp/tools) page.

## Prerequisites

* A NeetoDesk workspace and an account on it.
* An AI assistant that supports remote MCP servers. See [Connect](/mcp/connect) for the ones
  covered here.
* Optionally, a NeetoDesk API key. A key is needed only for workspace-scoped access. Every
  client listed on the Connect page can sign in with OAuth instead, so most people need no key
  at all.

## Which credential to use

This is a permissions boundary, not a setup preference, so it is worth deciding up front:

|           | OAuth                      | API key                          |
| --------- | -------------------------- | -------------------------------- |
| Scope     | The person who approved it | The whole workspace              |
| Identity  | A NeetoDesk user           | None                             |
| Set up by | Pasting the server URL     | Pasting a key into a config file |

[Authentication](/mcp/authentication) explains what each one can reach and why.

## Next steps

<CardGroup cols={2}>
  <Card title="Authentication" icon="lock" href="/mcp/authentication">
    OAuth, API keys and what each can see.
  </Card>

  <Card title="Connect" icon="plug" href="/mcp/connect">
    Per-client setup for Claude, ChatGPT, Cursor and the rest.
  </Card>

  <Card title="Examples" icon="comments" href="/mcp/examples">
    Prompts to try once you are connected.
  </Card>

  <Card title="Tools" icon="wrench" href="/mcp/tools">
    Every tool the server exposes.
  </Card>
</CardGroup>