Model Context Protocol

Solve tickets with the AI you already use.

One entry in Claude, ChatGPT, Cursor or any client that speaks MCP, and your assistant reads the queue, answers customers and, with Stripe connected, refunds and cancels. Everything it does happens as you.

Step 1

Sign in, or make a token

Apps that add a server by its address, like Claude and ChatGPT, ask you to sign in to NewDesk and pick the workspace. For a config file, press Make a token under Integrations; it is shown once.

Step 2

Paste one entry

The endpoint as a custom connector, or one server in your assistant's MCP config with the token as a bearer. The desk fills the snippet in for Claude Desktop, Claude Code and Cursor.

Step 3

Ask

"What is waiting in the queue?", "Answer #1042 and mark it solved", "Refund Jordan's last invoice". It reads, replies and acts as you, and it shows on the ticket under your name.

The one entry

A connector needs only the address. A config file carries a token, which the desk fills in; until then, YOUR_TOKEN stands where it goes.

Add custom connector
  Name: NewDesk
  URL:  https://newdesk.ai/api/mcp

Press Connect, sign in to NewDesk, pick the workspace, Allow.

Endpoint https://newdesk.ai/api/mcp. Streamable HTTP, JSON responses, OAuth 2.1 sign-in or a bearer token.

Works in

ClaudeA custom connector you sign in to, and Claude Code

ChatGPTConnectors you sign in to, on plans that allow them

CursorThe same entry in its MCP settings

VS CodeCopilot agent mode

GrokWhere it takes MCP servers

Anything elseStreamable HTTP, OAuth sign-in or a bearer token

Fifteen tools, the whole desk.

Reading the queue, answering, changing tickets, looking customers up, and with Stripe connected, the money. Two of them are real money and ask first.

desk_overviewHow the queue stands right now: open, pending, late, unassigned, solved today, and who is on the team.

list_ticketsTickets in the inbox, newest activity first, by status or by a saved view.

search_ticketsFind tickets by words in the subject, the customer, or the messages.

get_ticketOne ticket in full: the customer, the whole thread, and its state.

reply_to_ticketSend a reply to the customer, by the channel the ticket came in on, and mark it solved in the same breath if you like.

add_noteLeave an internal note. The customer never sees it.

update_ticketChange status, priority, who owns it, its tags.

create_ticketOpen a ticket for a customer, from a call or a conversation elsewhere.

search_customersFind customers by name, email or phone, with how many tickets each has.

customer_billingWhat Stripe knows about a customer: subscriptions and recent invoices.

refund_invoiceRefund a paid Stripe invoice, in full or in part. Real money: confirmed with the person asking first.

cancel_subscriptionCancel a Stripe subscription, at period end or now as the desk is set up. Confirmed first.

list_teamWho is on the team, their role, and whether they are at their desk right now.

knowledge_gapsQuestions the assistant could not answer from the knowledge base: what to write up next.

ask_assistantAsk the desk's own assistant a question, to check what a customer would be told.

Before you plug it in.

What it can do, what it will not do without you, and how to pull the plug.

Start free

Any of them. MCP tool calls are unlimited on Intro, Premium and Self-Owned alike, so the assistant can work the whole queue every day without a meter on it.

Your assistant, your inbox.

Unlimited tool calls on every license. Sign in from your assistant, or paste one entry, and ask.

Start free