Works with the Claude plan you already have

Solving tickets with Claude AI

Claude reads the conversation, checks your code, and drafts the reply in your voice. You say send.

Works with Claude — the Pro or Max plan you already have.

80 seconds. A real GoodSign customer question, answered from Claude Code.

What just happened

Nothing staged: a real customer, GoodSign’s real code, and the reply went out.

  1. The question

    Mark asks how to pre-fill a field through the API and lock it. Not a FAQ answer.

  2. One line

    “Pull down the latest issue from Mark Silcock.” Claude gets the whole thread.

  3. Checked against the code

    Claude reads the actual handler. The right answer, plus one gotcha the docs miss.

  4. Send it

    A draft in John’s voice. “Send it.” Mark has his answer.

Bug reports, fixed before they leave the page

A visitor reports a bug with a screenshot. get_conversation brings the report, the pages they were on and when, their browser and OS, and the screenshot itself into your terminal.

Claude Code is already in your source with your logs a command away — so it goes from “the button does nothing” to the line that broke it, fixes it, and drafts the reply. The customer hears back before you’ve switched windows.

$ claude
> check the latest message in tinyhelp — is that a bug?
●︎ tinyhelp — get_conversation(#3)
  Sarah: “the chat bubble isn’t showing on /pricing”
  screenshot.png · Chrome 126 · macOS
  pageviews: /pricing 2 min ago · /docs 6 min ago
✻ It is. pricing.html never loads w.js — the embed line
  is missing. Fixed and committed. Reply drafted in your
  voice — want me to send it?

Answer from wherever Claude is

The same connection works in the Claude app on your phone, on claude.ai and on the desktop. Ask what came in, read a thread, get a draft in your voice, say send — tiny.help doesn’t even need to be open.

Set your voice notes once and every draft reads like you wrote it, whichever device you’re holding.

Five tools. One rule.

tiny.help is a remote MCP server. Claude already knows how to use it; there’s nothing to install on your side beyond the connection.

You approve every send. That’s not a marketing line; it’s the instruction the server gives Claude with the send tool, every time:

“This delivers to a real person and cannot be unsent. Never use this tool to compose, preview, or ‘show’ a reply — write drafts in the chat as plain text instead. ‘Reply to #3’, ‘draft one’, silence, or your own suggestion to send are none of them approval. If you are unsure whether you have it, you do not — draft and ask instead.”
No autonomous agent answering your customers. A person reads the draft, and a person says send.

Connect once

Two ways in, depending on where you want your desk. Both use the same sign-in and the same access rules as the desk itself.

Claude Code

One computer, one command. Adds nothing to your Claude account or phone.

claude mcp add --transport http \
  tinyhelp https://desk.tiny.help/mcp
then /mcp → authenticate

Sign in with the Google account you use for your desk. From then on Claude Code can work a ticket while it’s sitting in your project’s code.

Phone, claude.ai and the desktop app

Added once in a browser, it’s on your whole Claude account.

  1. Open claude.ai → Settings → Connectors (Pro or Max plan).
  2. Add custom connector → paste the URL above.
  3. Sign in if asked — with the Google account you use for your desk. Whoever presses Allow is who Claude acts as.
  4. Press Allow. On your phone it now appears in a new chat under the + button → tools.

Questions

Do I need a Claude subscription?

For drafting, yes — a Claude Pro or Max plan, from Anthropic. Without it you still get the whole desk: the widget, the inbox, email in and out, push to your phone. You just write the replies yourself.

Does Claude ever send a reply on its own?

No. The send tool only accepts a reply you’ve already approved, and its own instructions tell Claude that a draft, “reply to #3”, or silence isn’t approval. If Claude is unsure whether it has approval, it doesn’t — it drafts and asks.

Does tiny.help read my source code?

No. tiny.help gives Claude the conversation — the messages, the visitor’s browser and pages, any screenshots. Claude Code reads your code because it’s running in your repository. That’s what makes the answer right.

Is tiny.help an MCP server?

Yes. A remote MCP server over HTTP at https://desk.tiny.help/mcp, with OAuth sign-in and the five tools above. It’s built for Claude Code, the Claude apps and claude.ai.

Can my teammates use it too?

Everyone on your desk connects with their own sign-in. Drafts come out in their voice notes, and a send is theirs — the customer sees who replied.

What does the connector cost?

It’s included on every plan — $29 a month for three sites and three people, with a 14-day trial. Drafting runs on your Claude plan.

Try it on your own inbox

Install the widget, connect Claude, and answer the next hard question from wherever you are. 14 days free, card up front, nothing charged until day 15.

Start your free 14-day trial