Zono Support

support.zonoPublished by zono.supportOfficial publisherv1.3.0Updated Oct 30, 2026

Work your Zono Support help desk from an AI client: tickets, customers, purchases and knowledge.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint for Zono Support that lets an AI client work a help desk: tickets, customers, purchases and knowledge.

What you can do
  • Work support tickets in the Zono help desk from an AI client.
  • Look up and manage customer records.
  • Access purchase information tied to support cases.
  • Use knowledge content held in Zono Support.
  • No individual tools are listed in the manifest, so exact actions are not documented here.
When to use it
Useful when a support team runs its help desk on Zono Support and wants an AI assistant to read or act on tickets, customers, purchases and knowledge without switching apps.
Requirements
A remote MCP endpoint at zono.support over streamable HTTP; no local package needed. A Zono account is required. Authentication is OAuth 2.1 with dynamic client registration, or an MCP token from the Zono account sent in the Authorization header as a Bearer token.
Before you install
The server can act on help desk data such as tickets, customers and purchases, so changes may affect real customer records; scope the token accordingly. The Authorization header carries a secret MCP token, so keep it out of logs and shared configs. OAuth sign-in grants the client access to the Zono account.

Installation

In SourceWeft

  1. Open Zono Support in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/support.zono%2Fzono-support/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "zono-support": {
      "type": "http",
      "url": "https://zono.support/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.3.0LatestOct 30, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.