Wonderchat

io.wonderchatPublished by wonderchat.ioOfficial publisherv1.1.0Updated Oct 30, 2026

AI help desk: set up a website support agent, train it, and work the ticket inbox.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Wonderchat's remote MCP server lets an assistant set up and train a website support agent and work its ticket inbox.

What you can do
  • Set up a website support agent and train it on site content.
  • Work the support ticket inbox, reading and handling incoming tickets.
  • No tool list is published, so exact actions are not documented; the server is described as an AI help desk for website support.
When to use it
Useful when a team runs its customer support on Wonderchat and wants an assistant to help configure the support agent or triage the ticket inbox without leaving the chat.
Requirements
Remote streamable HTTP endpoint at app.wonderchat.io; OAuth sign-in to a Wonderchat account is required. No environment variables or headers are declared.
Before you install
OAuth grants the assistant access to a Wonderchat workspace, which likely includes customer conversations and support content; actions on tickets may change or send replies. Review the granted scopes before connecting.

Installation

In SourceWeft

  1. Open Wonderchat 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/io.wonderchat%2Fwonderchat/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": {
    "wonderchat": {
      "type": "http",
      "url": "https://app.wonderchat.io/api/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.1.0LatestOct 30, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • 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.