Connect your assistant — Headless Desk

Connect your assistant

This desk has no app to sit in day to day. You work it by asking your assistant, which reaches it over MCP. It takes about a minute to set up.

YOUR ENDPOINT
https://desk.cleartrust.cc/mcp
01

Add it to your client

In Claude Code:

claude mcp add --transport http desk https://desk.cleartrust.cc/mcp

In any other client that supports MCP over HTTP, add https://desk.cleartrust.cc/mcp as a server. Clients that speak OAuth register themselves and send you here to sign in — you will see exactly what they are asking for before anything is granted.

02

Or use a key, if your client does not do OAuth

Create one on your account page and send it as a bearer token. It is shown once — only its hash is stored, so it cannot be read back afterwards.

Authorization: Bearer dskk_…
03

Then just ask

Your assistant learns the desk by calling discover, so you never have to know a field name or an operation. Things worth trying first:

“What's in my queue, worst first?”

“Anything about to breach in the next two hours?”

“Tell me everything about [email protected] before I reply.”

“Reply to #1042 saying the fix ships Thursday, then set it to pending.”

“Have we had this problem before?”

“How did we do on response targets last month, by priority?”

04

Point your support mailbox at it

Inbound mail arrives at POST https://desk.cleartrust.cc/inbound/email. Configure that as the delivery webhook in Plinth, and set PLINTH_WEBHOOK_SECRET to the value it will present — until that is set the route is closed rather than open.

Then set the support address on the team page, so the desk knows which mail is meant for it.


What it can do

Two tools. Everything goes through them.

discover

Learn the desk: the four tables, every field, the allowed values, and the full signature of every operation. Read-only, and the reason your assistant never has to guess a field name.

execute

Run any operation — opening tickets, replying, assigning, reporting, and plain reads and writes on every table. Supports a dry run that rolls itself back, and an idempotency key so a retry cannot act twice.

Everything you can reach is inside your own organisation. A key issued to you grants exactly what your account has, and revoking it takes effect on the next call.